Triple
T5679067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polylepis forest |
E125155
|
entity |
| Predicate | treeBarkTrait |
P29206
|
FINISHED |
| Object | multi-layered 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: multi-layered bark | Statement: [Polylepis forest, treeBarkTrait, multi-layered bark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treeBarkTrait Context triple: [Polylepis forest, treeBarkTrait, multi-layered bark]
-
A.
typicalLeafCharacteristic
Indicates the usual or defining features of a leaf that characterize it under normal conditions.
-
B.
treeVigor
Indicates the overall health, strength, and growth potential of a tree based on its physiological condition and environmental factors.
-
C.
forestCoverCharacteristic
chosen
Indicates a relationship where a forested area possesses a specific attribute or quality related to its tree or vegetation cover.
-
D.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
E.
isWoodyPlant
Indicates that the subject is a plant characterized by persistent, woody stems or trunks that remain above ground year-round.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.