Triple
T27494536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phyllostylon rhamnoides |
E693986
|
entity |
| Predicate | timberTradeName |
P151501
|
FINISHED |
| Object | palo blanco |
—
|
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: palo blanco | Statement: [Phyllostylon rhamnoides, timberTradeName, palo blanco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timberTradeName Context triple: [Phyllostylon rhamnoides, timberTradeName, palo blanco]
-
A.
woodTradeName
chosen
Indicates the commercial or trade name under which a particular type of wood is marketed or known.
-
B.
hasTradeName
Indicates that a product, substance, or entity is known or marketed under a specific commercial or brand name.
-
C.
isTradeNameOf
Indicates that one name is a commercial or brand designation used for a product, substance, or entity that may also have a different generic or formal name.
-
D.
tradingCompany
Indicates a relationship where an entity operates as a business engaged in buying, selling, or exchanging goods or services, typically across markets or regions.
-
E.
tradeNameIncludes
Indicates that a trade name contains another name or term as part of its full designation.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e8cb0c48190bbd8647a1fb6635b |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:07 p.m.