Triple
T24564615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 British & Irish Lions tour to New Zealand |
E607747
|
entity |
| Predicate | touringTeam |
P156350
|
FINISHED |
| Object | British & Irish Lions |
—
|
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: British & Irish Lions | Statement: [2005 British & Irish Lions tour to New Zealand, touringTeam, British & Irish Lions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touringTeam Context triple: [2005 British & Irish Lions tour to New Zealand, touringTeam, British & Irish Lions]
-
A.
racingTeam
Indicates that one entity is a racing team associated with, employing, or represented by the other entity in a competitive racing context.
-
B.
roadTeam
Indicates that the specified team is playing as the visiting (away) team in a given game or event.
-
C.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
D.
team1
Indicates that the referenced entity is the first team or side participating in a competitive or relational context.
-
E.
coachingTeam
Indicates that one entity serves as a coach or coaching staff for a particular team.
- F. None of above. chosen
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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f9d0f881909afc04537c32f76b |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:28 a.m.