Triple
T33112640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telcontar |
E847370
|
entity |
| Predicate | isQuenyaEquivalentOf |
P97511
|
FINISHED |
| Object | Strider |
—
|
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: Strider | Statement: [Telcontar, isQuenyaEquivalentOf, Strider]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isQuenyaEquivalentOf Context triple: [Telcontar, isQuenyaEquivalentOf, Strider]
-
A.
SindarinName
Indicates that one entity is the Sindarin (Elvish) name or designation of another entity.
-
B.
nameInQuenya
chosen
Indicates that an entity has a specific name expressed in the Quenya language.
-
C.
KhuzdulName
Indicates that an entity bears a name expressed in the Khuzdul (Dwarvish) language.
-
D.
nameCognateOf
Indicates that two names share a common linguistic origin or form, typically due to derivation from the same root or historical source.
-
E.
equivalentEpithetLanguage
Indicates that two epithets are expressed in different languages but convey the same meaning or designation.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6ec34a481908851cd68697cb88c |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.