Triple
T31003998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabethan |
E790014
|
entity |
| Predicate | notablePassengers |
P881
|
FINISHED |
| Object | Manchester United football team |
E909
|
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: Manchester United football team | Statement: [Elizabethan, notablePassengers, Manchester United football team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePassengers Context triple: [Elizabethan, notablePassengers, Manchester United football team]
-
A.
passengers
chosen
Indicates that one entity is traveling in or being transported by another entity, typically as a non-operating occupant.
-
B.
notablePersonnel
Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
-
C.
notableSpeciesInCrew
Indicates that a particular species is prominently represented or otherwise especially significant among the members of a crew.
-
D.
notablePilotOnRoute
Indicates that a particular pilot is notably associated with operating or having operated a specific route.
-
E.
notableCoPilotOnRoute
Indicates that an entity serves as a particularly recognized or distinguished co-pilot on a specific route.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a29183441a881909b5d2da676433345 |
completed | June 10, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:57 p.m.