Triple
T23473524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holarctic floristic region |
E570193
|
entity |
| Predicate | includesVegetationType |
P949
|
FINISHED |
| Object | taiga |
—
|
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: taiga | Statement: [Holarctic floristic region, includesVegetationType, taiga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesVegetationType Context triple: [Holarctic floristic region, includesVegetationType, taiga]
-
A.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
B.
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).
-
C.
containsPlantsWith
Indicates that one entity includes or holds within it one or more plant entities.
-
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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a70363488190bcbdedec5c2a945c |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:58 p.m.