Triple
T26390821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dowdall system |
E663406
|
entity |
| Predicate | firstPreferenceWeight |
P196536
|
FINISHED |
| Object | 1 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1 | Statement: [Dowdall system, firstPreferenceWeight, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPreferenceWeight Context triple: [Dowdall system, firstPreferenceWeight, 1]
-
A.
firstPreferenceShare
Indicates that one entity is the top-ranked or most preferred choice of another among multiple alternatives.
-
B.
secondPreferenceWeight
Indicates the relative importance or influence assigned to an entity when it is considered as a second preference in a choice or ranking.
-
C.
thirdPreferenceWeight
Indicates the relative importance or influence assigned to an entity when it is ranked as the third preference among multiple options.
-
D.
primaryCriterion
Indicates that one factor is designated as the main or most important basis for a decision, judgment, or selection among alternatives.
-
E.
givesFirstPickTo
Indicates that one entity grants another entity the right to choose first among available options.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
| PDg | Predicate description generation | batch_69fe5c196f4081908f150d4cd6c528fa |
completed | May 8, 2026, 9:56 p.m. |
Created at: April 26, 2026, 11:25 p.m.