Triple
T33067126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Stadium |
E846129
|
entity |
| Predicate | namedForAfterRenaming |
P133076
|
FINISHED |
| Object | Olympic sprinter Hasely Crawford |
—
|
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: Olympic sprinter Hasely Crawford | Statement: [National Stadium, namedForAfterRenaming, Olympic sprinter Hasely Crawford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForAfterRenaming Context triple: [National Stadium, namedForAfterRenaming, Olympic sprinter Hasely Crawford]
-
A.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
B.
formedByRenaming
chosen
Indicates that one entity is created or derived from another entity specifically through a change of name.
-
C.
namedAfterPattern
Indicates that one entity’s name is derived from or follows the naming convention or pattern established by another entity.
-
D.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
E.
changedNameAfter
Indicates that an entity adopted a different name following a specified time, event, or condition.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 1, 2026, 1:25 a.m.