Triple
T1379668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Theatre of Dreams |
E29307
|
entity |
| Predicate | isNicknameOf |
P25214
|
FINISHED |
| Object | Manchester United’s home ground |
—
|
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: Manchester United’s home ground | Statement: [The Theatre of Dreams, isNicknameOf, Manchester United’s home ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNicknameOf Context triple: [The Theatre of Dreams, isNicknameOf, Manchester United’s home ground]
-
A.
alsoKnownAs
Indicates that one entity is an alternative name, alias, or designation for another entity.
-
B.
notableNickname
chosen
Indicates that one entity is a well-known or widely recognized nickname or moniker for another entity.
-
C.
nameOf
Indicates that one entity is the name or designation of another entity.
-
D.
nameContrastsWith
Indicates that one name is deliberately chosen or used to highlight a difference or opposition in meaning, style, or identity relative to another name.
-
E.
nameGivesRiseTo
Indicates that one name, term, or designation leads to, causes, or results in the emergence or establishment of another.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c3187f248190a5813274b0ef944d |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befcabdc8190a9f05d002603f81c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.