Triple
T28890151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Tree of Gondor |
E732672
|
entity |
| Predicate | foundAsSaplingOn |
P8732
|
FINISHED |
| Object | slopes of Mindolluin |
—
|
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: slopes of Mindolluin | Statement: [White Tree of Gondor, foundAsSaplingOn, slopes of Mindolluin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundAsSaplingOn Context triple: [White Tree of Gondor, foundAsSaplingOn, slopes of Mindolluin]
-
A.
growsOn
Indicates that one entity develops or increases in size, number, or extent while being physically supported by or attached to another entity.
-
B.
plantedIn
Indicates that one entity has been placed or sown into another entity as its growing or containing medium.
-
C.
growsIn
chosen
Indicates that one entity develops, thrives, or increases in size or number within a specified environment, medium, or location.
-
D.
plantBecame
Indicates that an entity transitioned into or developed into a plant, changing its state or classification to that of a plant.
-
E.
foundUnder
Indicates that one entity is located beneath or below another entity in a way that it can be discovered or retrieved from that position.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 28, 2026, 7:54 a.m.