Triple
T32521359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloc B |
E831188
|
entity |
| Predicate | situatedWithinComplex |
P112021
|
FINISHED |
| Object | Résidence Palace, Brussels |
—
|
NE NERFINISHED |
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: Résidence Palace, Brussels | Statement: [Bloc B, situatedWithinComplex, Résidence Palace, Brussels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: situatedWithinComplex Context triple: [Bloc B, situatedWithinComplex, Résidence Palace, Brussels]
-
A.
housedWithinComplex
chosen
Indicates that one entity is located inside and functionally part of a larger building or facility complex.
-
B.
partOfTerminalComplex
Indicates that an entity functions as a component or subunit within a larger terminal complex structure.
-
C.
partOfResortComplexWith
Indicates that one entity is a component or facility within the same resort complex as the other entity, forming part of a shared resort property.
-
D.
locatedInBuildingOwnedBy
Indicates that one entity is situated within a building that is owned by another entity.
-
E.
isMainBuildingOf
Indicates that a building serves as the primary or central facility associated with a particular organization, complex, or site.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c50ec5848190a95efbea4fcd8861 |
completed | May 3, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.