Triple
T34640393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvan Elvish |
E889538
|
entity |
| Predicate | linguisticRoleInLegendarium |
P179554
|
FINISHED |
| Object | vernacular of woodland Elves |
—
|
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: vernacular of woodland Elves | Statement: [Silvan Elvish, linguisticRoleInLegendarium, vernacular of woodland Elves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linguisticRoleInLegendarium Context triple: [Silvan Elvish, linguisticRoleInLegendarium, vernacular of woodland Elves]
-
A.
roleInLegendarium
Indicates that one entity serves a particular narrative or functional role within the fictional mythos or legendarium associated with another entity.
-
B.
roleInWarOfTheRing
Indicates the specific function, position, or involvement an entity had within the events of the War of the Ring.
-
C.
SindarinName
Indicates that one entity is the Sindarin (Elvish) name or designation of another entity.
-
D.
nameInQuenya
Indicates that an entity has a specific name expressed in the Quenya language.
-
E.
raceInLegendarium
Indicates that an entity belongs to a particular fictional race or species within a specific mythological or fantasy legendarium.
- F. None of above. chosen
Provenance (4 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:04 a.m.