Triple
T25570794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctic tundra |
E640966
|
entity |
| Predicate | plantAdaptations |
P130825
|
FINISHED |
| Object | shallow root systems |
—
|
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: shallow root systems | Statement: [Arctic tundra, plantAdaptations, shallow root systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantAdaptations Context triple: [Arctic tundra, plantAdaptations, shallow root systems]
-
A.
typicalVegetationAdaptation
chosen
Indicates the characteristic ways in which vegetation is adapted to the prevailing environmental conditions of a given area.
-
B.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
C.
seedPlant
Indicates the action of placing seeds into soil or another growing medium to initiate the growth of plants.
-
D.
associatedFlora
Indicates a relationship where specific plants or vegetation are characteristically linked to, occur with, or are commonly found in association with a given entity or environment.
-
E.
plant
Indicates that an entity places or sets something firmly in or on a location, often so it will grow, remain fixed, or be established there.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8ffb11c8190add0643923c6eaf8 |
completed | May 2, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 3:57 p.m.