Triple
T30131521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Forest |
E765857
|
entity |
| Predicate | dominantTreeSpeciesBeforeAccident |
P80238
|
FINISHED |
| Object | Scots pine |
—
|
NE NERFINISHED |
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: Scots pine | Statement: [Red Forest, dominantTreeSpeciesBeforeAccident, Scots pine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantTreeSpeciesBeforeAccident Context triple: [Red Forest, dominantTreeSpeciesBeforeAccident, Scots pine]
-
A.
hasScientificNameOfDominantTree
Indicates the scientific (Latin) name of the tree species that is dominant in a given area or context.
-
B.
originalTreeFell
Indicates that the initially existing or primary tree has fallen down from its standing position.
-
C.
notableTreeSpecies
Indicates that the subject place or area is known for, or characterized by, the specified tree species.
-
D.
dominantTreeCommonName
chosen
Indicates the common (non-scientific) name of the tree species that is dominant in a given area or ecological context.
-
E.
dominantTree
Indicates that one tree has a dominant or prevailing influence over another tree, such as in size, canopy coverage, or competitive advantage within a shared environment.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 7:15 p.m.