Triple
T14142052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italy national rugby union team |
E350451
|
entity |
| Predicate | firstTestResult |
P58414
|
FINISHED |
| Object | Italy 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: Italy win | Statement: [Italy national rugby union team, firstTestResult, Italy win]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTestResult Context triple: [Italy national rugby union team, firstTestResult, Italy win]
-
A.
firstTest
Indicates that an entity is the initial or earliest test in a sequence or set of tests.
-
B.
testResult
chosen
Indicates that an entity has produced a specific outcome or value when subjected to a particular test or evaluation.
-
C.
firstTestLaunch
Indicates that an entity’s initial test launch event occurs, marking the first time it is experimentally deployed or sent into operation.
-
D.
firstTestYear
Indicates the year in which an entity’s first test or testing activity took place.
-
E.
centralTest
Indicates that an entity serves as the primary or core test within a set of tests or an evaluation process.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de611ed3508190add37baa30d1d134 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:48 a.m.