Triple
T3766187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coupe de France Final |
E82682
|
entity |
| Predicate | eligibilityOfCompetition |
P42315
|
FINISHED |
| Object | professional clubs |
—
|
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: professional clubs | Statement: [Coupe de France Final, eligibilityOfCompetition, professional clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibilityOfCompetition Context triple: [Coupe de France Final, eligibilityOfCompetition, professional clubs]
-
A.
eligibleCompetition
chosen
Indicates that an entity meets the required conditions to participate in a particular competition.
-
B.
appliesToCompetition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
-
C.
qualifyingCompetitionFor
Indicates that one competition serves as a qualifying event for participation in another competition.
-
D.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
E.
supportsCompetition
Indicates that one entity actively promotes, enables, or upholds the existence or functioning of competition 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc0004608190a810ae0270ae2478 |
completed | March 8, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.