Triple
T17074174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bièvres |
E414303
|
entity |
| Predicate | traversedBy |
P225
|
FINISHED |
| Object | Bièvre river |
E710023
|
NE 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: Bièvre river | Statement: [Bièvres, traversedBy, Bièvre river]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bièvre river Context triple: [Bièvres, traversedBy, Bièvre river]
-
A.
Bièvre
chosen
Bièvre is a small river in the Île-de-France region of northern France that flows through several suburbs southwest of Paris.
-
B.
Beuvron River
The Beuvron River is a watercourse in north-central France that flows through the Loiret department as a tributary of the Loire.
-
C.
Aure River
The Aure River is a small waterway in Normandy, northwestern France, that flows through the historic town of Bayeux before joining the Vire River.
-
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.
Orge River
The Orge River is a tributary of the Seine in northern France that flows through several towns in the Île-de-France region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc3b69c819093b32da3998eed46 |
completed | April 18, 2026, 7:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a017934b4e08190b54865802ead49fb |
completed | May 11, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:34 a.m.