Triple
T10914021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Girons |
E257773
|
entity |
| Predicate | departmentCapitalDistance |
P77414
|
FINISHED |
| Object | approximately 60 km from Foix |
—
|
LITERAL 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: approximately 60 km from Foix | Statement: [Saint-Girons, departmentCapitalDistance, approximately 60 km from Foix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: departmentCapitalDistance Context triple: [Saint-Girons, departmentCapitalDistance, approximately 60 km from Foix]
-
A.
distanceFromCapital
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
departmentCapitalOf
Indicates that a location serves as the administrative capital of a specified department (an administrative division).
-
C.
regionCapitalDistanceRelation
Indicates a relationship specifying the distance between a region and its capital.
-
D.
distanceToDepartmentCapital
chosen
Indicates the measured distance between a given location and the capital city of its corresponding department.
-
E.
districtHeadquartersDistance
Indicates the distance between a place and its corresponding district headquarters.
- F. None of above.
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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77073d12881908ea59771b84bc804 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d70d3f9dc88190a686a8b0dd6a3b21 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.