Triple
T9576084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innoventions |
E231048
|
entity |
| Predicate | buildingConfiguration |
P4394
|
FINISHED |
| Object | two connected pavilions |
—
|
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 connected pavilions | Statement: [Innoventions, buildingConfiguration, two connected pavilions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingConfiguration Context triple: [Innoventions, buildingConfiguration, two connected pavilions]
-
A.
buildingSystem
Indicates that one entity functions as a system, subsystem, or organized set of components that serves or supports the operation of a building.
-
B.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
C.
buildingSection
chosen
Indicates a relationship where one entity is a specific section, part, or subdivision of a larger building.
-
D.
buildingRedesignedBy
Indicates that a building has undergone a redesign carried out by the specified agent or designer.
-
E.
buildingComplex
Indicates a relationship where multiple buildings are grouped and function together as a single integrated complex.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99ac17a48190bb8448394f22b1e9 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.