Triple
T31336071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinus lagunae |
E799175
|
entity |
| Predicate | formsVegetationType |
P953
|
FINISHED |
| Object | montane pine woodland |
—
|
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: montane pine woodland | Statement: [Pinus lagunae, formsVegetationType, montane pine woodland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsVegetationType Context triple: [Pinus lagunae, formsVegetationType, montane pine woodland]
-
A.
vegetationType
chosen
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
B.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
C.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
D.
vegetationStructure
Indicates the structural characteristics or arrangement of plant life in an area, such as its layering, density, or complexity.
-
E.
hasVegetationRole
Indicates that an entity participates in or is assigned a specific functional role related to vegetation (such as growth, maintenance, or impact on plant life).
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 29, 2026, 9:16 p.m.