Triple
T21796352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canyon of Heroes |
E538103
|
entity |
| Predicate | hasHonorees |
P145682
|
FINISHED |
| Object | sports teams |
—
|
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: sports teams | Statement: [Canyon of Heroes, hasHonorees, sports teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHonorees Context triple: [Canyon of Heroes, hasHonorees, sports teams]
-
A.
hasNotableHonoree
Indicates that an entity is notably dedicated to, named after, or honors a particular person or group.
-
B.
honoreeHallOfFame
Indicates that an entity is recognized as an inductee or honoree in a particular Hall of Fame.
-
C.
includesHonoraryAwardsFor
Indicates that one entity contains or lists honorary awards that have been granted to another entity.
-
D.
honoreeField
Indicates that one entity is recognized or designated as the honoree associated with another entity, such as an award, event, or dedication.
-
E.
yearHonored
Indicates the specific year in which an entity received an honor, award, or formal recognition.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0622502188190998638317f232334 |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6c3a2898881909748935cf92f898c |
completed | April 21, 2026, 12:24 a.m. |
Created at: April 16, 2026, 6:53 p.m.