Triple
T3768149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L’Auto |
E82729
|
entity |
| Predicate | tourDeFranceRole |
P33874
|
FINISHED |
| Object | race 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: race organizer | Statement: [L’Auto, tourDeFranceRole, race organizer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourDeFranceRole Context triple: [L’Auto, tourDeFranceRole, race organizer]
-
A.
trackRole
Indicates that an entity holds or performs a specific role within the context of a particular track or sequence of activities.
-
B.
roleInExpedition
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
C.
roleInSeason
Indicates the specific role or function an entity has within a particular season of a series or competition.
-
D.
partyRoleOfFrance
Indicates the specific role or capacity that France holds as a party within a given agreement, event, or relationship.
-
E.
competitionRole
chosen
Indicates that an entity holds a specific role, position, or function within a competitive event or contest.
- 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_69adcc2bdf6c819088d3c6ace83ca5ea |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.