Triple
T26390826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dowdall system |
E663406
|
entity |
| Predicate | winnerCriterion |
P105632
|
FINISHED |
| Object | candidate with highest total Dowdall score |
—
|
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: candidate with highest total Dowdall score | Statement: [Dowdall system, winnerCriterion, candidate with highest total Dowdall score]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerCriterion Context triple: [Dowdall system, winnerCriterion, candidate with highest total Dowdall score]
-
A.
winnerType
Indicates the category or kind of winner associated with an event, competition, or outcome.
-
B.
winnerSelectionMethod
chosen
Indicates the process or criteria used to determine which participant is chosen as the winner.
-
C.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
-
D.
winnerManager
Indicates that one entity is the manager or supervisor of another entity who is the winner in a given context or competition.
-
E.
winnerRound
Indicates that an entity is the one who won a particular round in a multi-round event or competition.
- F. None of above.
Provenance (3 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_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 26, 2026, 11:25 p.m.