Triple
T37802466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest of Neldoreth |
E942414
|
entity |
| Predicate | treeTypeDominant |
P80238
|
FINISHED |
| Object | beech |
—
|
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: beech | Statement: [Forest of Neldoreth, treeTypeDominant, beech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treeTypeDominant Context triple: [Forest of Neldoreth, treeTypeDominant, beech]
-
A.
hasScientificNameOfDominantTree
Indicates the scientific (Latin) name of the tree species that is dominant in a given area or context.
-
B.
commonTreeType
Indicates that two or more entities share the same type or classification of tree.
-
C.
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.
-
D.
treeHabit
Indicates the growth form or structural habit characteristic of a tree, such as its typical shape, branching pattern, or overall stature.
-
E.
dominantTreeCommonName
chosen
Indicates the common (non-scientific) name of the tree species that is dominant in a given area or ecological context.
- 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_69f76ee6f1f4819091e2cf9c9e6aee19 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.