Triple
T35628308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fox (SmackDown era) |
E1029515
|
entity |
| Predicate | relatedEra |
P120335
|
FINISHED |
| Object | UPN (SmackDown era) |
E81954
|
NE 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: UPN (SmackDown era) | Statement: [Fox (SmackDown era), relatedEra, UPN (SmackDown era)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedEra Context triple: [Fox (SmackDown era), relatedEra, UPN (SmackDown era)]
-
A.
associatedWithNotableEra
Indicates that something has a significant connection or relevance to a historically or culturally notable period of time.
-
B.
associatedProductionEra
chosen
Indicates a relationship where something is linked to the specific time period or era during which it was produced or created.
-
C.
representedEra
Indicates the historical era or time period that something symbolizes, exemplifies, or stands for.
-
D.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
E.
followsEra
Indicates that one time period or era comes directly after another in chronological order.
- F. None of above.
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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38684ce02c8190bb6fcf1874dc245d |
completed | June 21, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.