Triple
T2995151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langdon |
E81047
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Langdonn |
E315693
|
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: Langdonn | Statement: [Langdon, hasSpellingVariant, Langdonn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Langdonn Context triple: [Langdon, hasSpellingVariant, Langdonn]
-
A.
Langden
chosen
Langden is an alternative spelling variant of the name Langdon, typically used as a surname or place name.
-
B.
Leintwardine
Leintwardine is a small historic village in Herefordshire, England, near the Welsh border, known for its Roman heritage and rural setting.
-
C.
Yattendon
Yattendon is a small village and civil parish in Berkshire, England, known for its rural character and historic buildings.
-
D.
Taverny
Taverny is a suburban commune in the northwestern outskirts of Paris, located in the Val-d'Oise department in northern France.
-
E.
Thérain
Thérain is a river in northern France that flows through the Oise department before joining the Oise River.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f2e5888190b3346012e2578dab |
completed | March 8, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b12e3bac408190b09bafee840eb0d1 |
completed | March 11, 2026, 8:56 a.m. |
Created at: March 8, 2026, 2:59 p.m.