Triple
T15387303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTT |
E367947
|
entity |
| Predicate | hasDomeDesign |
P118579
|
FINISHED |
| Object | innovative enclosure optimized for airflow and image quality |
—
|
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: innovative enclosure optimized for airflow and image quality | Statement: [NTT, hasDomeDesign, innovative enclosure optimized for airflow and image quality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomeDesign Context triple: [NTT, hasDomeDesign, innovative enclosure optimized for airflow and image quality]
-
A.
hasDomeStyle
Indicates that one entity (typically a building or structure) possesses a dome characterized by a particular architectural style or form.
-
B.
hasDomeDecoration
Indicates that an entity’s dome is adorned with specific decorative elements or ornamentation.
-
C.
hasDomeDesigner
Indicates that an entity’s dome was designed or created by a specific designer or architect.
-
D.
hasDomeMaterial
Indicates that the material specified is used as the primary construction or covering material of a dome.
-
E.
hasDomeColor
Indicates that an entity possesses a dome whose color matches the specified value.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e761b688190893a81246b735b76 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.