Triple
T36551035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torech Ungol |
E901256
|
entity |
| Predicate | pathOf |
P142543
|
FINISHED |
| Object | Gollum’s betrayal of Frodo |
—
|
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: Gollum’s betrayal of Frodo | Statement: [Torech Ungol, pathOf, Gollum’s betrayal of Frodo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pathOf Context triple: [Torech Ungol, pathOf, Gollum’s betrayal of Frodo]
-
A.
pathTo
chosen
Indicates that one entity serves as a route, way, or means of reaching, accessing, or moving to another entity.
-
B.
pathRepresents
Indicates that a given path symbolically stands for, encodes, or denotes another entity, concept, or structure.
-
C.
namespacePath
Indicates the hierarchical namespace location or route that defines where an entity is organized within a structured naming system.
-
D.
filePath
Indicates the relationship that specifies the location or directory path where a file is stored in a file system.
-
E.
pathFunction
Indicates a functional relationship that maps each point or state along a path to a corresponding value, position, or transformation defined by that path.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.