Triple
T27797513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier League 2011–12 with Manchester City |
E702153
|
entity |
| Predicate | cityRivals |
P906
|
FINISHED |
| Object | Manchester United F.C. |
—
|
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: Manchester United F.C. | Statement: [Premier League 2011–12 with Manchester City, cityRivals, Manchester United F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityRivals Context triple: [Premier League 2011–12 with Manchester City, cityRivals, Manchester United F.C.]
-
A.
cityRivalry
chosen
Indicates a competitive or adversarial relationship that exists between two cities, often involving sports, economics, culture, or historical tensions.
-
B.
game5City
Indicates that a particular game or sporting event took place in, or is associated with, a specific city.
-
C.
game6City
Indicates that a game or sporting event took place in, or is associated with, a particular city.
-
D.
rivalryInvolvesCity
Indicates that a rivalry relationship includes or is associated with a particular city as one of its involved locations.
-
E.
gangRival
Indicates that two gangs or gang-affiliated entities are in a state of rivalry or opposition to each other.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6380c776c8190afe636c9e65301a0 |
completed | May 2, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:32 p.m.