Triple
T24591941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howells & Hood |
E608560
|
entity |
| Predicate | competitionWinnerFor |
P156475
|
FINISHED |
| Object | Chicago Tribune Tower design competition |
—
|
NE NERFINISHED |
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: Chicago Tribune Tower design competition | Statement: [Howells & Hood, competitionWinnerFor, Chicago Tribune Tower design competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionWinnerFor Context triple: [Howells & Hood, competitionWinnerFor, Chicago Tribune Tower design competition]
-
A.
titleWinner
Indicates that an entity has won a specific title, championship, or formal award.
-
B.
winningPerformer
Indicates that the referenced performer is the one who achieved victory or first place in a particular competition, event, or contest.
-
C.
winnerProgram
Indicates that a program has achieved winning status in a competition, contest, or selection process.
-
D.
mainAwardWinner
Indicates that the subject is the primary recipient of a specified award or honor.
-
E.
ownedWinnerOf
Indicates that an entity owns or possesses the winner of a specified competition, contest, or event.
- 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_69e2c4cf54248190af7b0c2d9ade9830 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9dc63208190b70f57b9821a7241 |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:30 a.m.