Triple
T31601619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | soapbark tree |
E806361
|
entity |
| Predicate | partUsedCommercially |
P57217
|
FINISHED |
| Object | inner bark |
—
|
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: inner bark | Statement: [soapbark tree, partUsedCommercially, inner bark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partUsedCommercially Context triple: [soapbark tree, partUsedCommercially, inner bark]
-
A.
hasProductionUse
Indicates that something is utilized or applied within a production or operational environment.
-
B.
firstCommercialUse
Indicates the earliest point in time at which something was used commercially or put into commercial operation.
-
C.
partUsed
chosen
Indicates that one entity is a component or part that is utilized in the construction, operation, or composition of another entity.
-
D.
hasRetailUse
Indicates that an entity is used, intended, or designated for retail activities such as selling goods or services directly to consumers.
-
E.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a86aecd48190b0f9e9fcb4cab449 |
completed | May 3, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:33 p.m.