Triple
T12639685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coupe de France |
E301859
|
entity |
| Predicate | topTierEntryRound |
P106143
|
FINISHED |
| Object | round of 64 |
—
|
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: round of 64 | Statement: [Coupe de France, topTierEntryRound, round of 64]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topTierEntryRound Context triple: [Coupe de France, topTierEntryRound, round of 64]
-
A.
topTierFoundedAsRoundRobin
Indicates that a top-tier competition was originally established using a round-robin format.
-
B.
topTierUntil
Indicates that an entity holds a top-tier or highest-status position only up to a specified point in time, after which this status no longer applies.
-
C.
topDivisionLevel
Indicates that an entity belongs to the highest or primary division level within a hierarchical or organizational structure.
-
D.
topTierRelation
Indicates a relationship in which one entity belongs to the highest or most elite level within a ranked or hierarchical set of entities.
-
E.
topDivision
Indicates that an entity belongs to the highest-level division or tier within a hierarchical structure.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:16 p.m.