Triple
T36545075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephel Dúath |
E901117
|
entity |
| Predicate | partOfRangeSystemWith |
P52888
|
FINISHED |
| Object | Ered Lithui |
—
|
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: Ered Lithui | Statement: [Ephel Dúath, partOfRangeSystemWith, Ered Lithui]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfRangeSystemWith Context triple: [Ephel Dúath, partOfRangeSystemWith, Ered Lithui]
-
A.
partOfRange
chosen
Indicates that one entity is included within, or constitutes a segment of, the overall extent or span defined by another entity.
-
B.
partOfSystem
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
C.
isPartOfAccessSystem
Indicates that something functions as a component or element within a larger access control or access management system.
-
D.
isPartOfRepresentationSystem
Indicates that one entity functions as a component or element within a broader representational system (such as a notation, coding scheme, or symbolic framework).
-
E.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
- 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_6a0115fb84448190b8b67a5ace7b289a |
completed | May 10, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_6a0114ef60a081908f8db7868cf29b2f |
completed | May 10, 2026, 11:29 p.m. |
Created at: May 3, 2026, 4:11 p.m.