Triple
T21931368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brock Commons Tallwood House |
E541573
|
entity |
| Predicate | hasCoreMaterial |
P1845
|
FINISHED |
| Object | reinforced concrete |
—
|
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: reinforced concrete | Statement: [Brock Commons Tallwood House, hasCoreMaterial, reinforced concrete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreMaterial Context triple: [Brock Commons Tallwood House, hasCoreMaterial, reinforced concrete]
-
A.
hasReconstructionMaterial
Indicates that something is associated with, composed of, or utilizes a particular material for its reconstruction.
-
B.
hasMaterialType
chosen
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
C.
hasMaterialAspect
Indicates that something possesses a physical or tangible component or aspect as part of its overall nature or existence.
-
D.
hasSourceMaterial
Indicates that something is derived from, based on, or created using a particular source material.
-
E.
hasPremiumMaterials
Indicates that something is made from or includes higher-quality or superior-grade materials compared to standard options.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123ff16148190843d92bbc1e9bb24 |
completed | April 28, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:47 p.m.