Triple
T21370663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longpont-sur-Orge |
E527048
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Orge River |
—
|
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: Orge River | Statement: [Longpont-sur-Orge, locatedOn, Orge River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orge River Context triple: [Longpont-sur-Orge, locatedOn, Orge River]
-
A.
Orge River
chosen
The Orge River is a tributary of the Seine in northern France that flows through several towns in the Île-de-France region.
-
B.
Briance River
The Briance River is a watercourse in west-central France that flows through the Haute-Vienne department before joining the Vienne River.
-
C.
Buëch River
The Buëch River is a river in southeastern France that flows through the Alps and Provence regions before joining the Durance.
-
D.
Deûle River
The Deûle River is a canalised river in northern France that flows through the city of Lille and serves as an important waterway in the region.
-
E.
Beuvron River
The Beuvron River is a watercourse in north-central France that flows through the Loiret department as a tributary of the Loire.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0ae92c88190a3d3097f5b268a79 |
completed | April 22, 2026, 11:27 a.m. |
Created at: April 16, 2026, 5:10 p.m.