Triple
T32093128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 British & Irish Lions tour to New Zealand |
E819647
|
entity |
| Predicate | thirdTestResult |
P58414
|
FINISHED |
| Object | draw |
—
|
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: draw | Statement: [2017 British & Irish Lions tour to New Zealand, thirdTestResult, draw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdTestResult Context triple: [2017 British & Irish Lions tour to New Zealand, thirdTestResult, draw]
-
A.
thirdTestScore
Indicates the relationship where a specified test score is the third in an ordered sequence of test scores associated with an entity.
-
B.
testResult
chosen
Indicates that an entity has produced a specific outcome or value when subjected to a particular test or evaluation.
-
C.
thirdTestName
Indicates that an entity is associated with the name or label of its third test in a sequence of tests.
-
D.
thirdTestDate
Indicates the date on which a third test or testing event takes place in relation to an entity.
-
E.
testResultDisplay
Indicates how the outcome of a test is presented or shown to a viewer or system.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 12:25 a.m.