Triple
T19822592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arenastaden district |
E476232
|
entity |
| Predicate | hasEventInfrastructure |
P22000
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Arenastaden district, hasEventInfrastructure, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventInfrastructure Context triple: [Arenastaden district, hasEventInfrastructure, yes]
-
A.
hasAccessInfrastructure
Indicates that an entity is equipped with or connected to the physical or technical infrastructure necessary to access a particular service, resource, or network.
-
B.
hasEventSpace
chosen
Indicates that an entity provides or includes a designated space intended for hosting events.
-
C.
hasInfrastructureAbove
Indicates that one entity’s infrastructure is physically located above or over another entity.
-
D.
hasInfrastructurePeriod
Indicates the time period during which a particular piece of infrastructure exists, is in use, or is valid.
-
E.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654ffb37c8190be540a793befe16c |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.