Triple
T11714736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autoroute A89 |
E278465
|
entity |
| Predicate | connectsCity |
P4245
|
FINISHED |
| Object | Lyon |
E15889
|
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: Lyon | Statement: [Autoroute A89, connectsCity, Lyon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lyon Context triple: [Autoroute A89, connectsCity, Lyon]
-
A.
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.
-
B.
Lyon
Lyon is a historic Scottish noble family name most prominently associated with the Earls of Strathmore and Kinghorne.
-
C.
Lyons
Lyons is a small city in southeastern Georgia, United States, known as the administrative and commercial hub of Toombs County.
-
D.
Lyons
Lyons is a sports team or athletic program associated with Wheaton College, commonly referred to by this shortened name.
-
E.
Lyons
Lyons is a common English and Irish surname borne by numerous notable individuals across sports, politics, arts, and other fields.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4bf54d88190a8e07fbbf8d9e962 |
completed | April 10, 2026, 7:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68e9b70d08190aa74e612947317b5 |
completed | May 2, 2026, 11:54 p.m. |
Created at: April 8, 2026, 9:40 p.m.