Triple
T3768190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L’Auto |
E82730
|
entity |
| Predicate | roleInTourDeFrance |
P50999
|
FINISHED |
| Object | organizer |
—
|
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: organizer | Statement: [L’Auto, roleInTourDeFrance, organizer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTourDeFrance Context triple: [L’Auto, roleInTourDeFrance, organizer]
-
A.
roleInExpedition
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
roleInBordeaux
Indicates that an entity holds or has held a specific role, function, or position within the context of Bordeaux.
-
D.
roleInEurope
Indicates that an entity holds a specific function, position, or responsibility within a European context, such as within Europe as a region or its institutions.
-
E.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
- 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_69adcc2bdf6c819088d3c6ace83ca5ea |
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.