Triple
T18663845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siberian taiga |
E456273
|
entity |
| Predicate | understoryVegetation |
P69428
|
FINISHED |
| Object | mosses |
—
|
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: mosses | Statement: [Siberian taiga, understoryVegetation, mosses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: understoryVegetation Context triple: [Siberian taiga, understoryVegetation, mosses]
-
A.
commonUnderstorySpecies
chosen
Indicates that the related entities are species that commonly occur together in the understory layer of the same habitat or ecosystem.
-
B.
vegetationType
Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
-
C.
hasUnderstory
Indicates that one entity possesses or includes an understory layer beneath a main canopy or upper layer within it.
-
D.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
-
E.
vegetationStructure
Indicates the structural characteristics or arrangement of plant life in an area, such as its layering, density, or complexity.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5508c0d088190bef46fb3a3001f10 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.