Triple
T18284436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pico do Fogo |
E437945
|
entity |
| Predicate | usedForViticulture |
P131178
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pico do Fogo, usedForViticulture, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForViticulture Context triple: [Pico do Fogo, usedForViticulture, true]
-
A.
viticulturalUse
Indicates the way in which something is used or applied within the context of viticulture, such as grape growing or vineyard management practices.
-
B.
viticulturePractice
Indicates a relationship where a specific method, technique, or practice is used in the cultivation and management of grapevines.
-
C.
viticulturalFocus
Indicates a focus on or specialization in viticulture, i.e., activities, practices, or interests centered on grape growing and vineyard management.
-
D.
viticulturalFeature
Indicates a characteristic, condition, or attribute specifically related to grape growing or vineyard cultivation.
-
E.
hasViticulturalImportance
Indicates that something plays a significant role or has notable relevance in the cultivation and production of grapes for wine.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500f913d48190b41a1e37ca05e8b1 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.