Triple
T24406904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triple Crown |
E615334
|
entity |
| Predicate | originalCompetitionContext |
P90573
|
FINISHED |
| Object | Home Nations Championship |
—
|
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: Home Nations Championship | Statement: [Triple Crown, originalCompetitionContext, Home Nations Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCompetitionContext Context triple: [Triple Crown, originalCompetitionContext, Home Nations Championship]
-
A.
originalCompetitionName
Indicates the name of the competition as it was originally titled or first known, before any later changes or rebranding.
-
B.
hasCompetitionContext
chosen
Indicates that an entity is associated with or occurs within a specific competitive setting, event, or environment.
-
C.
usedInCompetitionContext
Indicates that something is employed or occurs within the setting, rules, or circumstances of a competition or contest.
-
D.
competitiveContext
Indicates a situation in which entities are engaged in or influenced by competition with one another.
-
E.
previousCompetition
Indicates that one competition occurred before another in time.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2957e8d5c8190bfed93aa308eb523 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.