Triple
T36206244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retour des cendres |
E1047403
|
entity |
| Predicate | ceremonialRouteStart |
P185056
|
FINISHED |
| Object | Courbevoie |
—
|
NE NERFINISHED |
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: Courbevoie | Statement: [Retour des cendres, ceremonialRouteStart, Courbevoie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialRouteStart Context triple: [Retour des cendres, ceremonialRouteStart, Courbevoie]
-
A.
ceremonialRoute
Indicates a route that is specifically used or designated for ceremonial, ritual, or formal processional purposes.
-
B.
openedAsCeremonialRoute
Indicates that a route was inaugurated or made accessible specifically for use in ceremonial or formal events.
-
C.
ceremonialAction
Indicates an action performed as part of a formal ceremony or ritual, typically following prescribed traditions or symbolic procedures.
-
D.
ceremonialProcession
Indicates a formal, often ritualized movement of people or objects in an organized sequence as part of a ceremony or official event.
-
E.
ceremonialCycle
Indicates a recurring sequence of rituals or formal events that are performed in a set order over a defined period.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb1d6b70819091227bd011734d19 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7ba6c27e081908868a2b50d1d603c |
completed | May 3, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:09 p.m.