Triple
T11759194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tour Perret |
E279608
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Gare d’Amiens |
E685038
|
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: Gare d’Amiens | Statement: [Tour Perret, near, Gare d’Amiens]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gare d’Amiens Context triple: [Tour Perret, near, Gare d’Amiens]
-
A.
Amiens railway station
chosen
Amiens railway station is the main rail hub of the city of Amiens in northern France, providing regional and intercity train connections.
-
B.
Gare de Compiègne
Gare de Compiègne is the main railway station serving the town of Compiègne in northern France, providing regional and intercity train connections.
-
C.
Gare de Sens
Gare de Sens is the main railway station serving the town of Sens in north-central France, providing regional and intercity train connections.
-
D.
Reims station
Reims station is the main railway station serving the city of Reims in northeastern France, providing regional and high-speed train connections.
-
E.
Meaux station
Meaux station is a railway station in Meaux, France, serving as a key regional hub for commuter and regional train services northeast of Paris.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a5220f148190ae60d1941a579ab6 |
completed | April 10, 2026, 7:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f16695479c819082c6ab12657a2d5f |
completed | April 29, 2026, 2:01 a.m. |
Created at: April 8, 2026, 9:41 p.m.