Triple
T10478523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marathon des Sables |
E247108
|
entity |
| Predicate | providedByOrganizer |
P94243
|
FINISHED |
| Object | water rations |
—
|
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: water rations | Statement: [Marathon des Sables, providedByOrganizer, water rations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedByOrganizer Context triple: [Marathon des Sables, providedByOrganizer, water rations]
-
A.
organizadoPor
Indicates that something is arranged, managed, or coordinated by a particular agent or entity.
-
B.
areOrganizedBy
Indicates that one entity is responsible for planning, coordinating, or managing the structure or execution of another entity or event.
-
C.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
-
D.
organizerRole
Indicates that an entity has the role or responsibility of organizing an event, activity, or group.
-
E.
principalOrganizer
Indicates that an entity serves as the main or leading organizer responsible for planning or coordinating another entity or event.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5095a25708190bf34e3ca1491e003 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:21 p.m.