Triple
T20910005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biosfera di Renzo Piano |
E514912
|
entity |
| Predicate | hasSteelStructure |
P141650
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Biosfera di Renzo Piano, hasSteelStructure, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSteelStructure Context triple: [Biosfera di Renzo Piano, hasSteelStructure, yes]
-
A.
isEngineeredStructure
Indicates that something is a man-made or artificially constructed structure, typically designed and built through engineering processes.
-
B.
isEngineeringStructureOf
Indicates that one entity serves as an engineering structure that is functionally or structurally associated with, or part of, another entity.
-
C.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
D.
hasBridgeOrStructure
Indicates that there exists a bridge or similar structural connection between the related entities.
-
E.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
- F. None of above. chosen
Provenance (4 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6ec5d73c88190a48180a1eed88190 |
completed | April 21, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:48 p.m.