Triple
T7904269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puntagorda |
E183531
|
entity |
| Predicate | hasNotableVegetation |
P949
|
FINISHED |
| Object | Canary Island pine forests |
—
|
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: Canary Island pine forests | Statement: [Puntagorda, hasNotableVegetation, Canary Island pine forests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableVegetation Context triple: [Puntagorda, hasNotableVegetation, Canary Island pine forests]
-
A.
hasAttractiveFoliage
Indicates that an entity possesses foliage that is visually appealing or ornamental in appearance.
-
B.
hasVegetationIssue
Indicates that an entity is affected by a problem, damage, or abnormal condition related to its vegetation or plant life.
-
C.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
D.
vegetation
chosen
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
E.
hasVegetationLayer
Indicates that an entity possesses a distinct layer or cover of vegetation as part of its structure or surface.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a4331cc8190b50301c78767a850 |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:02 p.m.