Triple
T14999463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitu tuberosum |
E374044
|
entity |
| Predicate | livesInStratum |
P14602
|
FINISHED |
| Object | forest understory |
—
|
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: forest understory | Statement: [Mitu tuberosum, livesInStratum, forest understory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesInStratum Context triple: [Mitu tuberosum, livesInStratum, forest understory]
-
A.
strataAre
Indicates that one or more entities are classified as geological or structural layers (strata) in relation to something else.
-
B.
containsStrataFrom
Indicates that one geological unit or object includes within it layers or strata originating from another specified source or unit.
-
C.
livesOn
Indicates that one entity resides or has its home on or atop another entity (such as a surface, structure, or geographic feature).
-
D.
livesInWorldWith
Indicates that one entity exists or resides within the same world or universe as another entity.
-
E.
foragingStratum
chosen
Indicates the vertical layer or height within a habitat where an organism typically searches for and obtains its food.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded71a5618819083ae96a79735ef98 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.