Triple
T15528873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aker Stadion |
E370155
|
entity |
| Predicate | nearestCityCentreDistance |
P78268
|
FINISHED |
| Object | short walking distance to Molde city centre |
—
|
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: short walking distance to Molde city centre | Statement: [Aker Stadion, nearestCityCentreDistance, short walking distance to Molde city centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestCityCentreDistance Context triple: [Aker Stadion, nearestCityCentreDistance, short walking distance to Molde city centre]
-
A.
nearestCityCenterDistance
chosen
Indicates the distance from a given location to the closest city center.
-
B.
nearestTownDistance
Indicates the distance from a given location to the closest town.
-
C.
nearestTownCenter
Indicates that one location is the closest town center to another specified point or area.
-
D.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
E.
administrativeCentreNearby
Indicates that an administrative centre is located close to the referenced entity in geographic or spatial terms.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0414620588190958ffde651ccab5f |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:05 a.m.