Triple
T7067871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worldwide Plaza |
E164607
|
entity |
| Predicate | integratesFunction |
P13995
|
FINISHED |
| Object | office space |
—
|
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: office space | Statement: [Worldwide Plaza, integratesFunction, office space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratesFunction Context triple: [Worldwide Plaza, integratesFunction, office space]
-
A.
integralTo
Indicates that one entity is an essential, non-removable component or part of another entity, such that the whole depends on it to function or be complete.
-
B.
integrates
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
C.
intendedFunction
chosen
Indicates that something is designed or purposed to perform a particular role, use, or function.
-
D.
integratesService
Indicates that one entity connects with and enables the functionality of another service so they work together as a unified system.
-
E.
combinedFunction
Indicates that multiple functions or operations are brought together and applied as a single, unified function or process.
- 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_69c6887b96548190a8a9b3ac8adf4119 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4a935488190a8c9c21bf30dd5d4 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:39 p.m.