Triple
T31690145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appalachian forest |
E808767
|
entity |
| Predicate | hasStratum |
P198190
|
FINISHED |
| Object | canopy 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: canopy layer | Statement: [Appalachian forest, hasStratum, canopy layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStratum Context triple: [Appalachian forest, hasStratum, canopy layer]
-
A.
strataAre
Indicates that one or more entities are classified as geological or structural layers (strata) in relation to something else.
-
B.
hasStratotype
Indicates that one entity serves as the designated standard or reference example (stratotype) for defining the stratigraphic characteristics of another entity.
-
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.
belongsToStratum
Indicates that something is a member or component of a particular layer, level, or stratum within a structured hierarchy or system.
- F. None of above. chosen
Provenance (4 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
| PDg | Predicate description generation | batch_69fed098328c819085979de6b179b378 |
completed | May 9, 2026, 6:13 a.m. |
Created at: April 30, 2026, 11:08 p.m.