Triple
T36206243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Retour des cendres |
E1047403
|
entity |
| Predicate | ceremonialRouteEnd |
P158428
|
FINISHED |
| Object | Hôtel des Invalides |
—
|
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: Hôtel des Invalides | Statement: [Retour des cendres, ceremonialRouteEnd, Hôtel des Invalides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialRouteEnd Context triple: [Retour des cendres, ceremonialRouteEnd, Hôtel des Invalides]
-
A.
ceremonialRoute
Indicates a route that is specifically used or designated for ceremonial, ritual, or formal processional purposes.
-
B.
ceremonialConclusion
Indicates the formal ending or closing phase of a ceremony or ritual.
-
C.
processionRouteEndsAt
chosen
Indicates that the endpoint or final destination of a procession’s route is a specified location.
-
D.
openedAsCeremonialRoute
Indicates that a route was inaugurated or made accessible specifically for use in ceremonial or formal events.
-
E.
ceremonialAction
Indicates an action performed as part of a formal ceremony or ritual, typically following prescribed traditions or symbolic procedures.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.