Triple
T13084847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fridhemsplan |
E310303
|
entity |
| Predicate | isBusyArea |
P91815
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fridhemsplan, isBusyArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBusyArea Context triple: [Fridhemsplan, isBusyArea, true]
-
A.
isBusyDuring
Indicates that an entity is occupied or engaged with some activity throughout a specified time period.
-
B.
isInArea
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
C.
isBusyLine
Indicates that a communication line or channel is currently in use and cannot accept additional connections or calls.
-
D.
isBusyHub
chosen
Indicates that a location or node functions as a central point of activity with a high volume of interactions, traffic, or connections.
-
E.
hasWaitingArea
Indicates that an entity provides or includes a designated space where people can wait before receiving a service or proceeding to another 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d981361e8c819099376435aa3a7aa3 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:02 p.m.