Triple
T32197675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schinopsis balansae |
E822442
|
entity |
| Predicate | woodDurabilityClass |
P1357
|
FINISHED |
| Object | very high 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: very high durability | Statement: [Schinopsis balansae, woodDurabilityClass, very high durability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: woodDurabilityClass Context triple: [Schinopsis balansae, woodDurabilityClass, very high durability]
-
A.
woodProperty
chosen
Indicates that one entity specifies or characterizes a property or attribute of wood associated with another entity.
-
B.
topWood
Indicates that one entity is made of or features a particular type of wood used specifically for its top surface or top section.
-
C.
hasWood
Indicates that one entity possesses, contains, or is made of wood in relation to another entity or context.
-
D.
woodTradeName
Indicates the commercial or trade name under which a particular type of wood is marketed or known.
-
E.
isWoodenStructure
Indicates that the subject is a structure primarily made of wood or constructed using wooden components.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb396ae081908d519ffc46252b1f |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:36 a.m.