Triple
T34640385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvan Elvish |
E889538
|
entity |
| Predicate | primaryUsersCulture |
P44820
|
FINISHED |
| Object | Silvan Elves of Mirkwood |
E897656
|
NE 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: Silvan Elves of Mirkwood | Statement: [Silvan Elvish, primaryUsersCulture, Silvan Elves of Mirkwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUsersCulture Context triple: [Silvan Elvish, primaryUsersCulture, Silvan Elves of Mirkwood]
-
A.
primaryCulture
chosen
Indicates the main or dominant culture associated with an entity, typically in contrast to any secondary or additional cultures.
-
B.
primaryLocalLanguageFamily
Indicates the main linguistic family to which the predominant local language of an entity belongs.
-
C.
primaryLocaleType
Indicates the main or default locale category associated with an entity, such as its primary language or regional setting.
-
D.
usedCulture
Indicates that one entity employed, applied, or drew upon the cultural practices, norms, or artifacts associated with another entity.
-
E.
defaultCulture
Indicates that one culture is designated as the primary or standard culture used by default in a given context or system.
- F. None of above.
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_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b25155b481908528f65804b5b123 |
completed | June 21, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:04 a.m.