Triple
T18059596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasagatan |
E432135
|
entity |
| Predicate | runsThroughArea |
P34612
|
FINISHED |
| Object | central Stockholm |
—
|
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: central Stockholm | Statement: [Vasagatan, runsThroughArea, central Stockholm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsThroughArea Context triple: [Vasagatan, runsThroughArea, central Stockholm]
-
A.
passesThroughArea
chosen
Indicates that an entity moves or extends through the spatial region defined by another entity or area.
-
B.
runsThroughNeighborhood
Indicates that something (such as a route, path, or service) passes through or traverses a particular neighborhood.
-
C.
runsAcross
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
-
D.
runsInto
Indicates that one entity moves so as to collide or come into sudden contact with another entity.
-
E.
runsAround
Indicates that one entity moves in a circular or surrounding path around another entity or area.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c10583648190a161c58abf4853d5 |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.