Triple
T38285105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canvas Stadium |
E1022183
|
entity |
| Predicate | namedAfterFieldHonors |
P46466
|
FINISHED |
| Object | Sonny Lubick |
—
|
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: Sonny Lubick | Statement: [Canvas Stadium, namedAfterFieldHonors, Sonny Lubick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterFieldHonors Context triple: [Canvas Stadium, namedAfterFieldHonors, Sonny Lubick]
-
A.
nameHonors
chosen
Indicates that a name is given to honor, commemorate, or pay tribute to a particular entity.
-
B.
namedInHonorBy
Indicates that one entity has been used as the namesake or dedicatee by another entity, signifying that the latter is named in honor of the former.
-
C.
namedAwardAfter
Indicates that an award has been given a name in honor of or derived from a particular person, group, or entity.
-
D.
namedAfterAwardYear
Indicates that one entity is named after the year in which a particular award was given or received.
-
E.
honoreeField
Indicates that one entity is recognized or designated as the honoree associated with another entity, such as an award, event, or dedication.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: May 3, 2026, 4:30 p.m.