Triple
T2032242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larix |
E44542
|
entity |
| Predicate | woodDurability |
P1357
|
FINISHED |
| Object | high natural durability |
—
|
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: high natural durability | Statement: [Larix, woodDurability, high natural durability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: woodDurability Context triple: [Larix, woodDurability, high natural durability]
-
A.
woodProperty
chosen
Indicates that one entity specifies or characterizes a property or attribute of wood associated with another entity.
-
B.
hardiness
Indicates the degree to which an entity can withstand or endure harsh, adverse, or challenging conditions.
-
C.
designedToWithstand
Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
-
D.
exteriorMaterial
Indicates the material that forms the outer surface or outer construction of an object or structure.
-
E.
mechanicalDurability
Indicates the ability of something to withstand mechanical forces, stresses, or wear without failing or degrading.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9313134819088133fb69b8f606f |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.