Triple
T32955770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neuville-sur-Saône |
E843094
|
entity |
| Predicate | locatedInDepartmentFormer |
P85528
|
FINISHED |
| Object | Rhône department |
E78793
|
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: Rhône department | Statement: [Neuville-sur-Saône, locatedInDepartmentFormer, Rhône department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDepartmentFormer Context triple: [Neuville-sur-Saône, locatedInDepartmentFormer, Rhône department]
-
A.
locatedInModernDepartment
Indicates that an entity is geographically situated within the boundaries of a present-day administrative department.
-
B.
formerDepartment
Indicates that one entity previously served as a department or subunit of another entity but no longer holds that status.
-
C.
basedInDepartment
Indicates that an entity operates or has its primary affiliation within a specific department.
-
D.
locatedAtFormer
Indicates that an entity is currently located at a place where another entity was previously located.
-
E.
locatedWithinFormer
chosen
Indicates that one entity is or was geographically contained within the boundaries of another entity that no longer exists in its former administrative or territorial form.
- F. None of above.
Provenance (4 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a03460f3a8c8190ae3f4cd69e0e54d9 |
completed | May 12, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34d278d4d88190a83d385a45f3cd59 |
completed | June 19, 2026, 5:24 a.m. |
| PD | Predicate disambiguation | batch_6a0345810b3481908aec06ab2b712e12 |
completed | May 12, 2026, 3:21 p.m. |
Created at: May 1, 2026, 1:21 a.m.