Triple
T32093127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 British & Irish Lions tour to New Zealand |
E819647
|
entity |
| Predicate | secondTestResult |
P58414
|
FINISHED |
| Object | British & Irish Lions win |
—
|
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: British & Irish Lions win | Statement: [2017 British & Irish Lions tour to New Zealand, secondTestResult, British & Irish Lions win]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondTestResult Context triple: [2017 British & Irish Lions tour to New Zealand, secondTestResult, British & Irish Lions win]
-
A.
secondTestScore
Indicates the score an entity received on its second test or assessment in a sequence.
-
B.
secondTestName
Indicates that an entity serves as the second named test or secondary test designation associated with another entity.
-
C.
testResult
chosen
Indicates that an entity has produced a specific outcome or value when subjected to a particular test or evaluation.
-
D.
secondSeriesTestName
Indicates that an entity is associated with the name or label of a second test series in a sequence of tests.
-
E.
secondTestSeriesDate
Indicates the date on which the second test in a series is scheduled or took place.
- 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_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 1, 2026, 12:25 a.m.