Triple
T5611909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Browns Stadium |
E147376
|
entity |
| Predicate | revertedName |
P16337
|
FINISHED |
| Object | Cleveland Browns Stadium in 2023 |
—
|
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: Cleveland Browns Stadium in 2023 | Statement: [Cleveland Browns Stadium, revertedName, Cleveland Browns Stadium in 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revertedName Context triple: [Cleveland Browns Stadium, revertedName, Cleveland Browns Stadium in 2023]
-
A.
nameRestored
chosen
Indicates that an entity’s original or correct name has been reinstated after having been changed, lost, or altered.
-
B.
formerName
Indicates that an entity was previously known by a different name in the past.
-
C.
returnedToName
Indicates that an entity has gone back or been sent back to a specific person or named recipient.
-
D.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
-
E.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0211fad448190b068b77ed25931d5 |
completed | March 22, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.