Triple
T9385263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howea forsteriana |
E225888
|
entity |
| Predicate | airPurifying |
P88639
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Howea forsteriana, airPurifying, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airPurifying Context triple: [Howea forsteriana, airPurifying, yes]
-
A.
ventilationFeature
Indicates that one entity has a structural or functional role related to providing, enabling, or affecting ventilation for another entity.
-
B.
purifiedBy
Indicates that something has been cleansed, refined, or made pure through the action or process performed by another agent or method.
-
C.
airIntakeType
Indicates the type or configuration of the system or mechanism used to draw air into an engine or device.
-
D.
airService
Indicates that an air transportation service (such as flights or air routes) is provided or operates between the related entities.
-
E.
hasAtmosphericArrangement
Indicates that one entity possesses or exhibits a particular configuration or structure of atmospheric components or layers in relation to another entity or defined standard.
- F. None of above. chosen
Provenance (4 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d142008190840e131e8f1940f9 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:44 p.m.