Triple
T34693354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taur-nu-Fuin |
E890957
|
entity |
| Predicate | etymologyLanguageFamily |
P42488
|
FINISHED |
| Object | Elvish |
—
|
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: Elvish | Statement: [Taur-nu-Fuin, etymologyLanguageFamily, Elvish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: etymologyLanguageFamily Context triple: [Taur-nu-Fuin, etymologyLanguageFamily, Elvish]
-
A.
etymologicalLanguageFamily
chosen
Indicates that one entity is the language family from which the other entity is etymologically derived or historically originates.
-
B.
etymologicalLanguage
Indicates the language from which a word or term is historically derived in its etymology.
-
C.
etymologyRelatesTo
Indicates a relationship where one term’s origin, history, or derivation is connected to another linguistic form, word, or source.
-
D.
derivedFromLanguageFamily
Indicates that one language originates from, or historically descends from, a particular language family.
-
E.
languageFamilyBranchOf
Indicates that one language family branch is a sub-group or subdivision within a larger language family.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f723549ac8819088816d0c96e28251 |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.