Triple
T22886535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brookfield Place (Calgary) |
E567617
|
entity |
| Predicate | complexComponents |
P86680
|
FINISHED |
| Object | two office towers |
—
|
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: two office towers | Statement: [Brookfield Place (Calgary), complexComponents, two office towers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complexComponents Context triple: [Brookfield Place (Calgary), complexComponents, two office towers]
-
A.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
B.
isTotallyComplex
Indicates that something possesses a level of complexity that is complete, multifaceted, and not reducible to simpler or purely real/straightforward components.
-
C.
complexName
Indicates that an entity has a multi-part or structurally intricate name, typically composed of several elements or components.
-
D.
hasComplexification
Indicates that one entity is a more complex or elaborated version, form, or development of another entity.
-
E.
componentCC
chosen
Indicates that one entity is a component or constituent part of another entity within a coordinated or composite construction.
- 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_69e2458a92ec81908fc1cd5f6407d2ab |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17fc1e3408190833a062afbea509d |
completed | April 29, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:40 p.m.