Triple
T15655748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torvastad |
E376433
|
entity |
| Predicate | countyCapitalDistance |
P69055
|
FINISHED |
| Object | approximately 70 km north of Stavanger |
—
|
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 70 km north of Stavanger | Statement: [Torvastad, countyCapitalDistance, approximately 70 km north of Stavanger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countyCapitalDistance Context triple: [Torvastad, countyCapitalDistance, approximately 70 km north of Stavanger]
-
A.
hasCountyCapitalDistance
chosen
Indicates a distance relationship specifying how far a county is from its capital.
-
B.
distanceFromCapital
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
C.
regionCapitalDistanceRelation
Indicates a relationship specifying the distance between a region and its capital.
-
D.
stateCapitalProximity
Indicates the spatial closeness or distance between a state’s capital city and another specified location.
-
E.
distanceToProvinceCapital_km
Indicates the distance, measured in kilometers, between a given location and the capital city of its province.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef1f83c8190bbf65eed162cbd55 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.