Triple
T24406906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triple Crown |
E615334
|
entity |
| Predicate | currentCompetitionContext |
P3228
|
FINISHED |
| Object | Six 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: Six Nations Championship | Statement: [Triple Crown, currentCompetitionContext, Six Nations Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentCompetitionContext Context triple: [Triple Crown, currentCompetitionContext, Six Nations Championship]
-
A.
currentNameOfCompetition
Indicates that an entity is the present, official name by which a particular competition is currently known.
-
B.
hasCompetitionContext
Indicates that an entity is associated with or occurs within a specific competitive setting, event, or environment.
-
C.
leagueContext
chosen
Indicates the broader league or competition setting within which the relationship or action takes place.
-
D.
competitionStatus
Indicates the current state or phase of a competition, such as whether it is upcoming, ongoing, paused, or completed.
-
E.
servedCompetition
Indicates that one entity provided service, participation, or representation in a competitive event or context involving another entity.
- 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.