Triple
T6328685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burseraceae |
E141920
|
entity |
| Predicate | woodProduct |
P1272
|
FINISHED |
| Object | okoumé plywood (from Aucoumea klaineana) |
—
|
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: okoumé plywood (from Aucoumea klaineana) | Statement: [Burseraceae, woodProduct, okoumé plywood (from Aucoumea klaineana)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: woodProduct Context triple: [Burseraceae, woodProduct, okoumé plywood (from Aucoumea klaineana)]
-
A.
woodProperty
Indicates that one entity specifies or characterizes a property or attribute of wood associated with another entity.
-
B.
furniture
Indicates that one entity is a piece of furniture associated with, located in, or used by another entity.
-
C.
materialUsed
chosen
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
D.
hasDoorMaterial
Indicates that an entity’s door is made of, or primarily composed of, a specified material.
-
E.
forestryActivity
Indicates activities related to the management, use, or cultivation of forest resources, such as logging, planting, or forest maintenance.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0651197908190a30e504e2442d40f |
completed | March 22, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.