Triple
T21745788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophie Piper |
E536782
|
entity |
| Predicate | hasMagicLineage |
P145208
|
FINISHED |
| Object | Cromwell witches |
—
|
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: Cromwell witches | Statement: [Sophie Piper, hasMagicLineage, Cromwell witches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagicLineage Context triple: [Sophie Piper, hasMagicLineage, Cromwell witches]
-
A.
hasPriestlyLineage
Indicates that an entity descends from, or belongs to, a recognized priestly family or hereditary priestly line.
-
B.
isRelictLineage
Indicates that an entity represents a surviving remnant of an otherwise extinct evolutionary lineage.
-
C.
basedOnCharacterLineage
Indicates that one entity is derived from, inspired by, or determined according to the ancestral or familial lineage of a character.
-
D.
hasMortalOrSemiDivineAncestry
Indicates that an entity descends from, or is otherwise ancestrally connected to, beings who are mortal or possess semi-divine (partly divine) status.
-
E.
hasLimitedMagic
Indicates that an entity possesses magical abilities that are restricted in scope, power, frequency, or conditions of use.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a76540c8190b91a67f4a70869fb |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69f3ed4408190a4a78410bf660c44 |
completed | April 20, 2026, 9:48 p.m. |
Created at: April 16, 2026, 6:49 p.m.