Triple
T9505400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarthe |
E229255
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Orne |
E123324
|
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: Orne | Statement: [Sarthe, borders, Orne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orne Context triple: [Sarthe, borders, Orne]
-
A.
Orne
chosen
Orne is a rural department in northwestern France known for its pastoral landscapes, horse breeding, and historic towns such as Alençon.
-
B.
Orne River
The Orne River is a waterway in northwestern France that flows through Normandy before emptying into the English Channel at the port town of Ouistreham.
-
C.
Olne
Olne is a small municipality in the province of Liège in Wallonia, eastern Belgium, known for its rural character and traditional village charm.
-
D.
The Nore
The Nore is a sandbank at the mouth of the Thames Estuary in England that historically served as a major Royal Navy anchorage and site of naval command.
-
E.
Tejn
Tejn is a small coastal town and fishing port on the Danish island of Bornholm in the Baltic Sea.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9850fe6c8190a5a96cfae12562c6 |
completed | April 1, 2026, 10:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d13a1de2d88190a6a10379d2297510 |
completed | April 4, 2026, 4:19 p.m. |
Created at: March 30, 2026, 7:57 p.m.