Triple
T27622374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canary Island pine |
E700610
|
entity |
| Predicate | waterAcquisition |
P11699
|
FINISHED |
| Object | captures moisture from clouds |
—
|
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: captures moisture from clouds | Statement: [Canary Island pine, waterAcquisition, captures moisture from clouds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterAcquisition Context triple: [Canary Island pine, waterAcquisition, captures moisture from clouds]
-
A.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
B.
waterSourceType
chosen
Indicates the kind or category of source from which water is obtained.
-
C.
sourceOfWaterSupply
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
D.
waterSourceDedicatedTo
Indicates that a particular water source is specifically allocated or reserved for a designated use, group, or purpose.
-
E.
waterSourceAccessibility
Indicates how easily and reliably water sources can be reached, obtained, and used by intended users.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 27, 2026, 2:15 p.m.