Triple
T30785878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | アスタナ・ハンシャティル |
E783952
|
entity |
| Predicate | 構造エンジニアリング |
P123497
|
FINISHED |
| Object | 英国企業Buro Happoldが関与 |
—
|
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: 英国企業Buro Happoldが関与 | Statement: [アスタナ・ハンシャティル, 構造エンジニアリング, 英国企業Buro Happoldが関与]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 構造エンジニアリング Context triple: [アスタナ・ハンシャティル, 構造エンジニアリング, 英国企業Buro Happoldが関与]
-
A.
isEngineeringStructureOf
Indicates that one entity serves as an engineering structure that is functionally or structurally associated with, or part of, another entity.
-
B.
structuralDesign
Indicates the relationship in which an entity is responsible for planning, organizing, or defining the structural configuration or framework of another entity.
-
C.
engineeringBasis
Indicates that something serves as the foundational technical or engineering rationale, justification, or underlying basis for another entity or decision.
-
D.
engineeringDesign
Indicates the relationship in which an entity is responsible for planning, specifying, or creating the technical design of another entity (such as a system, component, or structure).
-
E.
structuralDesigner
chosen
Indicates that an entity is responsible for planning, analyzing, and designing the structural aspects of another entity (such as a building, bridge, or component).
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fe8168c8190b083be0e33988b9c |
completed | May 2, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:41 p.m.