Triple
T1149320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akershus Fortress |
E23638
|
entity |
| Predicate | cityGateTo |
P26079
|
FINISHED |
| Object | medieval Oslo |
—
|
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: medieval Oslo | Statement: [Akershus Fortress, cityGateTo, medieval Oslo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityGateTo Context triple: [Akershus Fortress, cityGateTo, medieval Oslo]
-
A.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
B.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
C.
roadNetworkHubOf
Indicates that one location functions as a central node or hub within the road network relative to another location or area.
-
D.
isDowntownEndpointOf
Indicates that a location serves as the downtown terminus or endpoint of a route, line, or path.
-
E.
roadAccessFrom
Indicates that one location can be reached from another via a usable road connection.
- F. None of above. chosen
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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bd0ab5f88190bb583fc63b4cc150 |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:44 p.m.