Triple
T32072230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LB Châteauroux |
E819042
|
entity |
| Predicate | notableCompetitionAppearance |
P99442
|
FINISHED |
| Object | UEFA Intertoto Cup |
E36598
|
NE 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: UEFA Intertoto Cup | Statement: [LB Châteauroux, notableCompetitionAppearance, UEFA Intertoto Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCompetitionAppearance Context triple: [LB Châteauroux, notableCompetitionAppearance, UEFA Intertoto Cup]
-
A.
competitionInNotableEvent
Indicates that an entity participated as a competitor in a specific notable event or competition.
-
B.
tournamentAppearances
Indicates the number of times an entity has participated in a particular tournament or competition.
-
C.
featuredInCompetition
chosen
Indicates that an entity was included or showcased as a participant or entry in a specific competition.
-
D.
competedAs
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
-
E.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
- F. None of above.
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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2edde7555c81909e181aed708ad4fd |
completed | June 14, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:23 a.m.