Triple
T29150597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheriff Graham Humbert |
E738895
|
entity |
| Predicate | hasCursedIdentity |
P141639
|
FINISHED |
| Object | Sheriff of Storybrooke |
—
|
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: Sheriff of Storybrooke | Statement: [Sheriff Graham Humbert, hasCursedIdentity, Sheriff of Storybrooke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCursedIdentity Context triple: [Sheriff Graham Humbert, hasCursedIdentity, Sheriff of Storybrooke]
-
A.
cursedIdentityOf
chosen
Indicates that one entity is the cursed or negatively transformed identity or form of another entity.
-
B.
hasCursedLocation
Indicates a relationship where a location is affected by or associated with a curse.
-
C.
hasSecretIdentity
Indicates that an entity possesses an alternate, hidden identity that is not publicly known.
-
D.
hasMysteriousPast
Indicates that an entity possesses a past that is unknown, hidden, or only partially revealed, often implying secrets or unexplained events.
-
E.
hasDemonCharacter
Indicates that an entity includes or features a character that is a demon.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 28, 2026, 11:42 a.m.