Triple
T3527318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seine-Maritime |
E74571
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Seine River |
E6962
|
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: Seine River | Statement: [Seine-Maritime, namedAfter, Seine River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seine River Context triple: [Seine-Maritime, namedAfter, Seine River]
-
A.
River Seine
chosen
The River Seine is a major waterway in northern France that flows through the heart of Paris and is central to the city's history, culture, and landscape.
-
B.
Source-Seine
Source-Seine is the small commune in eastern France where the River Seine originates.
-
C.
Baie de Seine
Baie de Seine is a coastal bay in northern France where the Seine River meets the English Channel, known for its maritime traffic and proximity to ports like Le Havre.
-
D.
Oise River
The Oise River is a major waterway in northern France and southern Belgium that flows into the Seine and serves as an important route for inland navigation and commerce.
-
E.
Seine-Inférieure
Seine-Inférieure was a former department in northern France, largely corresponding to today’s Seine-Maritime in the Normandy 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc6d099c8190b2b1e65a56e52089 |
completed | March 8, 2026, 6:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdf9f26be48190bf21b252a922ca69 |
completed | March 21, 2026, 1:52 a.m. |
Created at: March 8, 2026, 3:19 p.m.