Triple
T18759574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embankment |
E458733
|
entity |
| Predicate | occupiesSpace |
P2574
|
FINISHED |
| Object | interior of Turbine Hall |
—
|
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: interior of Turbine Hall | Statement: [Embankment, occupiesSpace, interior of Turbine Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupiesSpace Context triple: [Embankment, occupiesSpace, interior of Turbine Hall]
-
A.
occupies
chosen
Indicates that one entity takes up or resides within a physical or conceptual space belonging to or associated with another entity.
-
B.
occupiedBy
Indicates that a space, position, or role is currently being used, held, or filled by a particular entity.
-
C.
occupiesBlock
Indicates that one entity is physically positioned within or taking up space in a specified block or bounded area.
-
D.
occupiedFrom
Indicates that an entity is in use or inhabited starting from a specified point in time.
-
E.
spaceRequirements
Indicates the amount and type of physical or storage space needed for something to be properly placed, installed, or operated.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d7db2f48190a4f1c5c9801fe180 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.