Triple
T33789365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATLANTIDE Organisation Internationale |
E865888
|
entity |
| Predicate | roleInMarathonDesSables |
P24306
|
FINISHED |
| Object | founder |
—
|
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: founder | Statement: [ATLANTIDE Organisation Internationale, roleInMarathonDesSables, founder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInMarathonDesSables Context triple: [ATLANTIDE Organisation Internationale, roleInMarathonDesSables, founder]
-
A.
roleInTourDeFrance
Indicates the specific capacity or function an entity has within the context of the Tour de France (e.g., rider, team, official, or support role).
-
B.
roleInExpedition
chosen
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
C.
tourRole
Indicates the specific function, capacity, or responsibility an entity has within the context of a tour.
-
D.
roleInMissions
Indicates the specific function, duty, or position an entity holds within one or more missions.
-
E.
roleInRescue
Indicates the specific function or responsibility an entity has within a rescue operation or event.
- 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00a602b6b48190a9dea8ae22d2fa05 |
completed | May 10, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_6a00a559bf3881909a7b50776d8f47bb |
completed | May 10, 2026, 3:33 p.m. |
Created at: May 1, 2026, 1:45 a.m.