Triple
T2600136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of the Dead |
E58320
|
entity |
| Predicate | numberOfKnownSpells |
P39519
|
FINISHED |
| Object | approximately 190 |
—
|
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: approximately 190 | Statement: [Book of the Dead, numberOfKnownSpells, approximately 190]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfKnownSpells Context triple: [Book of the Dead, numberOfKnownSpells, approximately 190]
-
A.
spells
Indicates that one entity writes or names the letters of a word or sequence in their correct order for another entity or context.
-
B.
typeOfMagic
Indicates that one entity is a specific category, school, or kind of magic associated with another entity.
-
C.
numberOfKnownPlays
Indicates the total count of plays that are known to be associated with a given entity (such as an author, theater, or period).
-
D.
spokenIncantation
Indicates that an entity has uttered a specific magical or ritual phrase, typically to invoke an effect or power.
-
E.
hasRitualFocus
Indicates that an entity is associated with or directed toward a particular object, practice, or element that serves as the central focus of a ritual.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd457564c819080d8c8818c02545a |
completed | March 7, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69abd0d4e8648190b612eb09aa085451 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1c7b6e48190be9a0c31069df797 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:49 p.m.