Triple
T35511626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Daggerfall Covenant |
E1026297
|
entity |
| Predicate | memberCulture |
P8961
|
FINISHED |
| Object | Kingdom of Daggerfall |
—
|
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: Kingdom of Daggerfall | Statement: [The Daggerfall Covenant, memberCulture, Kingdom of Daggerfall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberCulture Context triple: [The Daggerfall Covenant, memberCulture, Kingdom of Daggerfall]
-
A.
groupCulture
Indicates that a group shares common norms, values, practices, or traditions that characterize its collective way of life.
-
B.
usesCulture
Indicates that one entity employs, incorporates, or relies on the cultural practices, norms, or artifacts associated with another entity in its actions or functioning.
-
C.
hasCulturalCommunity
chosen
Indicates that an entity is associated with, belongs to, or is part of a specific cultural community.
-
D.
cultureOfOrigin
Indicates the cultural background or tradition from which an entity originates or is derived.
-
E.
usedCulture
Indicates that one entity employed, applied, or drew upon the cultural practices, norms, or artifacts associated with another entity.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: May 3, 2026, 4:04 p.m.