Triple
T16749979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beograđanka |
E407046
|
entity |
| Predicate | topFloorUsedFor |
P44317
|
FINISHED |
| Object | observation and technical facilities |
—
|
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: observation and technical facilities | Statement: [Beograđanka, topFloorUsedFor, observation and technical facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topFloorUsedFor Context triple: [Beograđanka, topFloorUsedFor, observation and technical facilities]
-
A.
hasUpperFloorUse
chosen
Indicates that an entity’s upper floor is assigned or designated for a particular use or function.
-
B.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
-
C.
numberOfFloors
Indicates the total count of distinct floor levels that a building or structure has.
-
D.
hasFloorUse
Indicates that a particular floor or level of a building is designated for a specific function, activity, or type of use.
-
E.
floorCount
Indicates the number of floors or levels that a building or structure has.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa265a908190a87fa4612bfe6396 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.