Triple
T1686690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auvers-sur-Oise |
E36457
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Oise River |
E47853
|
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: Oise River | Statement: [Auvers-sur-Oise, locatedOn, Oise River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oise River Context triple: [Auvers-sur-Oise, locatedOn, Oise River]
-
A.
Allier River
The Allier River is a major river in central France, known for its largely unspoiled natural course and as a tributary of the Loire.
-
B.
Loir
The Loir is a river in central France that flows through the regions of Pays de la Loire and Centre-Val de Loire before joining the Sarthe.
-
C.
Semois River
The Semois River is a picturesque waterway in southern Belgium and northern France, known for winding through the rugged, forested landscapes of the Ardennes.
-
D.
Oise
chosen
Oise is a major river in northern France that flows through regions such as Picardy and Île-de-France before joining the Seine near Paris.
-
E.
Sarthe River
The Sarthe River is a waterway in western France that flows through the regions of Normandy and Pays de la Loire before joining other rivers to form the Maine.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa6293c368819094ab0f615e418647 |
completed | March 6, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af2b4b974081908da05bc63f923215 |
completed | March 9, 2026, 8:19 p.m. |
Created at: March 4, 2026, 7:29 p.m.