Triple
T29578860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itinéraire de Paris à Jérusalem |
E753518
|
entity |
| Predicate | describesJourneyTo |
P21947
|
FINISHED |
| Object | Jerusalem |
—
|
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: Jerusalem | Statement: [Itinéraire de Paris à Jérusalem, describesJourneyTo, Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesJourneyTo Context triple: [Itinéraire de Paris à Jérusalem, describesJourneyTo, Jerusalem]
-
A.
journeyFrom
Indicates that an entity undertakes or originates a journey starting from a specified location or source.
-
B.
timeOfJourneyDescribed
Indicates that the predicate specifies the particular time period or duration during which the described journey takes place.
-
C.
journeyDestination
chosen
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
D.
journeyFunction
Indicates a relationship where an entity serves as the purpose, role, or functional objective of a journey or travel event.
-
E.
structureOfJourney
Indicates the way a journey is organized or arranged, including the sequence and relationships between its stages or segments.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 28, 2026, 6:05 p.m.