Triple
T35013857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosmeri pantheon |
E1010000
|
entity |
| Predicate | primaryStorytellerDeity |
P118406
|
FINISHED |
| Object | Y'ffre |
E1009350
|
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: Y'ffre | Statement: [Bosmeri pantheon, primaryStorytellerDeity, Y'ffre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStorytellerDeity Context triple: [Bosmeri pantheon, primaryStorytellerDeity, Y'ffre]
-
A.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
B.
roleOfReferencedDeity
chosen
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
C.
typeOfDeity
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
D.
otherDeity
Indicates that one deity is distinct from and not identical to another deity within a given context or system.
-
E.
fictionalDeity
Indicates that one entity is regarded as a deity or god that exists only within a fictional or mythological context created by another entity 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37fb00cf208190a084940b253a9f25 |
completed | June 21, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.