Triple
T17021997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Apartments (Stockholm Palace) |
E412967
|
entity |
| Predicate | locatedInFloor |
P74241
|
FINISHED |
| Object | principal floor |
—
|
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: principal floor | Statement: [Royal Apartments (Stockholm Palace), locatedInFloor, principal floor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFloor Context triple: [Royal Apartments (Stockholm Palace), locatedInFloor, principal floor]
-
A.
locatedOnLevel
chosen
Indicates that one entity is situated on a specific floor or level within a multi-level structure or system.
-
B.
locatedInBuildingFloorCount
Indicates that one entity is located in or associated with a building characterized by a specific number of floors.
-
C.
locatedInSectionOfBuilding
Indicates that one entity is situated within a specific section or area of a building.
-
D.
occupiesFloorsOf
Indicates that one entity uses or takes up multiple levels or stories within a building or structure.
-
E.
locatedOnBuilding
Indicates that one entity is physically situated on the exterior or rooftop surface of a building.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d1d2e48190bbcba129247c6c2e |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.