Triple
T3295200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rungis |
E69197
|
entity |
| Predicate | distanceToParisCenter_km |
P10703
|
FINISHED |
| Object | approximately 11 |
—
|
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: approximately 11 | Statement: [Rungis, distanceToParisCenter_km, approximately 11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToParisCenter_km Context triple: [Rungis, distanceToParisCenter_km, approximately 11]
-
A.
distanceFromParisCenter
chosen
Indicates the measured distance between a given location and the central point of Paris.
-
B.
distanceFromParisSaintLazare
Indicates the physical distance between a given place and Paris Saint-Lazare railway station.
-
C.
distanceToFrance
Indicates the spatial distance between a given entity and the country of France.
-
D.
distanceToMetzKilometers
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Metz.
-
E.
distanceFromToulouse
Indicates the measured spatial distance between a given entity and the location of Toulouse.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb077c60c81909782be5202ce5a43 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.