Triple
T3959877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Constructivism |
E85874
|
entity |
| Predicate | emphasizedMaterial |
P1272
|
FINISHED |
| Object | industrial materials |
—
|
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: industrial materials | Statement: [Russian Constructivism, emphasizedMaterial, industrial materials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizedMaterial Context triple: [Russian Constructivism, emphasizedMaterial, industrial materials]
-
A.
thematicMaterial
Indicates that one entity serves as the primary recurring idea, motif, or thematic content that is developed or referenced by another entity.
-
B.
featuresMaterialFrom
Indicates that one entity incorporates, contains, or is composed of material originating from another entity.
-
C.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
hasEmphasis
Indicates that one element is given special stress, importance, or prominence relative to others.
-
E.
material
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:31 p.m.