Triple
T18111026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkshire Cup |
E433472
|
entity |
| Predicate | groupStatusIntroduced |
P130489
|
FINISHED |
| Object | 1971 |
—
|
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: 1971 | Statement: [Yorkshire Cup, groupStatusIntroduced, 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupStatusIntroduced Context triple: [Yorkshire Cup, groupStatusIntroduced, 1971]
-
A.
introducedStatus
Indicates that one entity has brought another entity or concept into use, awareness, or existence within a particular context or system.
-
B.
settingIntroducedIn
Indicates the work, installment, or context in which a particular setting first appears or is established.
-
C.
hasGroupStatus
Indicates that an entity possesses a particular status, role, or condition within a group or collective context.
-
D.
introducedForState
Indicates that something was created, proposed, or brought forward specifically for use in or application to a particular state.
-
E.
hasPopulationStatus
Indicates the current demographic condition or classification of a population associated with an entity.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd2038081909515fb6d17495cbf |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:28 a.m.