Triple
T36072835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eucalyptus obliqua |
E1043410
|
entity |
| Predicate | barkPersistence |
P51881
|
FINISHED |
| Object | rough bark on trunk and larger branches |
—
|
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: rough bark on trunk and larger branches | Statement: [Eucalyptus obliqua, barkPersistence, rough bark on trunk and larger branches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: barkPersistence Context triple: [Eucalyptus obliqua, barkPersistence, rough bark on trunk and larger branches]
-
A.
barkIs
Indicates that an entity produces the characteristic sound associated with barking.
-
B.
barkProperty
chosen
Indicates that an entity possesses a characteristic or quality related to bark (such as texture, color, or pattern).
-
C.
barkUsedFor
Indicates that the bark of something is utilized for a particular purpose or function.
-
D.
barkContains
Indicates that one piece of bark physically includes or encloses another substance, object, or portion of bark within its structure or boundaries.
-
E.
barkTendency
Indicates a tendency or propensity for an entity to bark, such as how likely or frequently it engages in barking behavior.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.