Triple
T12592489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Germain-en-Laye |
E300640
|
entity |
| Predicate | positionRelativeToParis |
P45843
|
FINISHED |
| Object | western suburbs of Paris |
—
|
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: western suburbs of Paris | Statement: [Saint-Germain-en-Laye, positionRelativeToParis, western suburbs of Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToParis Context triple: [Saint-Germain-en-Laye, positionRelativeToParis, western suburbs of Paris]
-
A.
elevationRelativeToParis
Indicates the relative elevation difference between a given location and Paris, specifying how much higher or lower it is in altitude.
-
B.
distanceFromParisCenter
Indicates the measured distance between a given location and the central point of Paris.
-
C.
directionFromParis
chosen
Indicates the cardinal or relative compass direction of an entity as measured from Paris toward that entity.
-
D.
distanceFromParisSaintLazare
Indicates the physical distance between a given place and Paris Saint-Lazare railway station.
-
E.
positionRelativeToEarth
Indicates the spatial position or orientation of an entity in relation to the Earth as a reference frame.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:07 p.m.