Triple
T19389121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyons, New York |
E485014
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Lyon, France |
—
|
NE NERFINISHED |
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: Lyon, France | Statement: [Lyons, New York, namedAfter, Lyon, France]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lyon, France Context triple: [Lyons, New York, namedAfter, Lyon, France]
-
A.
Lyon, Rhône, France
Lyon, Rhône, France is a major historic city in east-central France known for its rich cultural heritage, gastronomy, and role as an important economic and industrial center.
-
B.
Leon, France
Leon, France is a French locality whose name was used as the namesake for the town of Leon in Iowa, United States.
-
C.
Lyon
Lyon is a historic Scottish noble family name most prominently associated with the Earls of Strathmore and Kinghorne.
-
D.
Lyon
chosen
Lyon is a major city in east-central France known for its historical and architectural landmarks, gastronomy, and role as a key economic and cultural center.
-
E.
Lyons
Lyons is a small town in northern Colorado known as a gateway to the Rocky Mountains and for its vibrant music and arts scene.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b425e848190ab5ae8ae0a034fe2 |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.