Triple
T9508677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howea belmoreana |
E229334
|
entity |
| Predicate | indoorUseReason |
P21011
|
FINISHED |
| Object | attractive foliage |
—
|
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: attractive foliage | Statement: [Howea belmoreana, indoorUseReason, attractive foliage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indoorUseReason Context triple: [Howea belmoreana, indoorUseReason, attractive foliage]
-
A.
reasonForUse
chosen
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
B.
indoorOrOutdoor
Indicates whether an activity, event, or entity occurs inside a building (indoors) or outside in open air (outdoors).
-
C.
hasIndoorArea
Indicates that an entity possesses or includes an area or space that is located indoors or within a building.
-
D.
partOfUse
Indicates that something functions as a component or constituent within the use or application of something else.
-
E.
houseUse
Indicates how a house or dwelling is used or purposed (e.g., residential, commercial, mixed-use).
- 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.