Triple
T3768729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tour Voile |
E82743
|
entity |
| Predicate | isTeamCompetition |
P51022
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tour Voile, isTeamCompetition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTeamCompetition Context triple: [Tour Voile, isTeamCompetition, yes]
-
A.
hasNumberOfTeams
Indicates the quantity of teams associated with or contained by a given entity.
-
B.
includesCompetition
Indicates that one entity contains, features, or encompasses a competition as part of its scope or content.
-
C.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
D.
isDomesticCompetitionForAssociation
Indicates that a competition is a national or internal event organized under the authority of a specific sports association or governing body.
-
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. 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc2d4b848190bf63fb3ed5d3b2d9 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc133ef50819094c2b971f31f1615 |
completed | March 8, 2026, 6:34 p.m. |
Created at: March 8, 2026, 3:35 p.m.