Triple
T18513727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Deciduous Forest |
E452406
|
entity |
| Predicate | typicalUnderstoryPlant |
P69428
|
FINISHED |
| Object | dogwood (Cornus spp.) |
—
|
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: dogwood (Cornus spp.) | Statement: [Eastern Deciduous Forest, typicalUnderstoryPlant, dogwood (Cornus spp.)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUnderstoryPlant Context triple: [Eastern Deciduous Forest, typicalUnderstoryPlant, dogwood (Cornus spp.)]
-
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.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
D.
hasUnderstory
Indicates that one entity possesses or includes an understory layer beneath a main canopy or upper layer within it.
-
E.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53348274c8190a82861b0104538e3 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.