Triple
T21048287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akersgata |
E518506
|
entity |
| Predicate | hasAdjacentBuildingUse |
P70406
|
FINISHED |
| Object | administrative |
—
|
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: administrative | Statement: [Akersgata, hasAdjacentBuildingUse, administrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentBuildingUse Context triple: [Akersgata, hasAdjacentBuildingUse, administrative]
-
A.
hasNeighboringBuilding
Indicates that one building is located adjacent to or directly next to another building.
-
B.
adjacentBuildingFunction
chosen
Indicates that two buildings located next to each other have a specified functional relationship or usage connection.
-
C.
hasBuildingUseAlongStreet
Indicates that a building located along a particular street is used for a specified purpose or function in relation to that street.
-
D.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
E.
hasBuildingStyleInSurroundings
Indicates that an entity is surrounded by or located in an area characterized by a particular building style.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf5b01481909db49aa5be3846aa |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:34 p.m.