Triple
T24564622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 British & Irish Lions tour to New Zealand |
E607747
|
entity |
| Predicate | testSeriesResult |
P156351
|
FINISHED |
| Object | New Zealand won 3–0 |
—
|
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: New Zealand won 3–0 | Statement: [2005 British & Irish Lions tour to New Zealand, testSeriesResult, New Zealand won 3–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testSeriesResult Context triple: [2005 British & Irish Lions tour to New Zealand, testSeriesResult, New Zealand won 3–0]
-
A.
testSeriesOf
Indicates that one entity is a test or evaluation designed to be applied sequentially or collectively to a series of related entities.
-
B.
testSeriesRole
Indicates the specific role or function an entity has within a test series or sequence of tests.
-
C.
testResult
Indicates that an entity has produced a specific outcome or value when subjected to a particular test or evaluation.
-
D.
testResultDisplay
Indicates how the outcome of a test is presented or shown to a viewer or system.
-
E.
testSeriesPurpose
Indicates that a test series is conducted with the specific purpose or objective of achieving a particular outcome or goal.
- 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.