Triple
T9508656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howea belmoreana |
E229334
|
entity |
| Predicate | typicalIndoorHeight |
P573
|
FINISHED |
| Object | up to about 2–3 m |
—
|
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: up to about 2–3 m | Statement: [Howea belmoreana, typicalIndoorHeight, up to about 2–3 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalIndoorHeight Context triple: [Howea belmoreana, typicalIndoorHeight, up to about 2–3 m]
-
A.
typicalHeight
chosen
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
B.
floorHeight
Indicates the vertical elevation or level at which a particular floor is positioned within a structure.
-
C.
ceilingHeight
Indicates the vertical distance from the floor to the ceiling in a given space.
-
D.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
E.
heightAboveSurroundings
Indicates that an entity’s vertical position or elevation is higher than that of its immediate surrounding area.
- 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.