Triple
T38569067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Lothlórien |
E928310
|
entity |
| Predicate | associatedWithTreeType |
P68706
|
FINISHED |
| Object | mallorn trees |
—
|
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: mallorn trees | Statement: [Lord of Lothlórien, associatedWithTreeType, mallorn trees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTreeType Context triple: [Lord of Lothlórien, associatedWithTreeType, mallorn trees]
-
A.
associatedWithTree
chosen
Indicates a relationship in which an entity is connected or related to a tree, such as by location, origin, use, or interaction.
-
B.
commonTreeType
Indicates that two or more entities share the same type or classification of tree.
-
C.
mainTreeType
Indicates the predominant type of tree that characterizes or dominates a given area, object, or context.
-
D.
hasForestAssociation
Indicates an ecological or contextual relationship in which an entity is associated with, influenced by, or characteristically occurs in forest environments.
-
E.
associatedWithSacredTree
Indicates a relationship in which an entity is linked or connected to a sacred tree, such as by location, significance, use, or ritual association.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.