Triple
T6650586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Steel Design Award |
E150808
|
entity |
| Predicate | materialEmphasized |
P618
|
FINISHED |
| Object | structural steel |
—
|
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: structural steel | Statement: [European Steel Design Award, materialEmphasized, structural steel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: materialEmphasized Context triple: [European Steel Design Award, materialEmphasized, structural steel]
-
A.
designEmphasizes
Indicates that a design intentionally places special importance or focus on a particular feature, principle, or aspect over others.
-
B.
hasEmphasis
Indicates that one element is given special stress, importance, or prominence relative to others.
-
C.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
D.
material
chosen
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
-
E.
materialDescribedAs
Indicates that a material is characterized or specified using a particular descriptive term, label, or textual description.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.