Triple
T35321553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allochrocebus lhoesti |
E1020050
|
entity |
| Predicate | usesStrata |
P123547
|
FINISHED |
| Object | ground layer |
—
|
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: ground layer | Statement: [Allochrocebus lhoesti, usesStrata, ground layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStrata Context triple: [Allochrocebus lhoesti, usesStrata, ground layer]
-
A.
strataAre
Indicates that one or more entities are classified as geological or structural layers (strata) in relation to something else.
-
B.
preferredStrata
chosen
Indicates the geological or social layers that an entity most favors, prioritizes, or tends to occupy or interact with over others.
-
C.
containsStrataFrom
Indicates that one geological unit or object includes within it layers or strata originating from another specified source or unit.
-
D.
hasStrataCountApprox
Indicates that an entity has an approximate or estimated number of strata (layers), rather than an exact count.
-
E.
stratificationRole
Indicates the role or function an entity plays within a hierarchical or layered structure used to organize or classify elements.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 3, 2026, 4:03 p.m.