Triple
T9508658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howea belmoreana |
E229334
|
entity |
| Predicate | crownDescription |
P10697
|
FINISHED |
| Object | dense crown of arching fronds |
—
|
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: dense crown of arching fronds | Statement: [Howea belmoreana, crownDescription, dense crown of arching fronds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crownDescription Context triple: [Howea belmoreana, crownDescription, dense crown of arching fronds]
-
A.
crownType
chosen
Indicates the specific style or form of a crown associated with an entity.
-
B.
crownRepresents
Indicates that one entity (the crown) symbolically stands for, embodies, or serves as an official emblem of another entity, such as authority, sovereignty, or a governing body.
-
C.
crownColor
Indicates the color attribute of an entity’s crown or top part.
-
D.
crownedWith
Indicates that one entity serves as a crown, top, or decorative upper covering placed upon another entity.
-
E.
crownPosition
Indicates the relative placement or orientation of a crown with respect to another object or reference point.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9855c5e48190a7d8d39b6d601679 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:58 p.m.