Triple
T24564640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 British & Irish Lions tour to New Zealand |
E607747
|
entity |
| Predicate | secondTestDate |
P43539
|
FINISHED |
| Object | 2005-07-02 |
—
|
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: 2005-07-02 | Statement: [2005 British & Irish Lions tour to New Zealand, secondTestDate, 2005-07-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondTestDate Context triple: [2005 British & Irish Lions tour to New Zealand, secondTestDate, 2005-07-02]
-
A.
secondTestSeriesDate
chosen
Indicates the date on which the second test in a series is scheduled or took place.
-
B.
secondReachedDate
Indicates the date on which the second specified event, state, or condition is reached or occurs.
-
C.
secondCoupDate
Indicates the date on which an entity experienced or carried out its second coup.
-
D.
secondAttackDate
Indicates the date on which a second attack or follow-up assault occurred in relation to a prior initial attack.
-
E.
secondRoundDate
Indicates the date on which the second round of an event, process, or sequence is scheduled or occurs.
- 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_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. |
Created at: April 18, 2026, 2:28 a.m.