Triple
T35013828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosmeris |
E1009999
|
entity |
| Predicate | hasOriginInLore |
P188875
|
FINISHED |
| Object | Aldmeri linguistic roots |
—
|
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: Aldmeri linguistic roots | Statement: [Bosmeris, hasOriginInLore, Aldmeri linguistic roots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginInLore Context triple: [Bosmeris, hasOriginInLore, Aldmeri linguistic roots]
-
A.
hasOriginStoryLocation
Indicates that an entity’s origin story takes place at or is associated with a specific location.
-
B.
hasHistoricalOrigin
Indicates that something originated, was first established, or came into existence during a specific historical period or context.
-
C.
hasFolkloreStatus
Indicates that something is recognized or classified as having a status or role within folklore or traditional cultural narratives.
-
D.
hasNarrativeOrigin
chosen
Indicates that something originates from, is derived from, or is based on a particular narrative or story.
-
E.
hasLoreContext
Indicates that something is associated with or situated within a particular narrative, historical, or fictional background or storyline.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: May 3, 2026, 4:01 p.m.