Triple
T35507345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursula Zandt |
E1026185
|
entity |
| Predicate | realNameInCanon |
P9233
|
FINISHED |
| Object | Sally Juspeczyk |
—
|
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: Sally Juspeczyk | Statement: [Ursula Zandt, realNameInCanon, Sally Juspeczyk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realNameInCanon Context triple: [Ursula Zandt, realNameInCanon, Sally Juspeczyk]
-
A.
hasFullNameInCanon
Indicates that an entity’s complete, official name is explicitly established within the canonical source material.
-
B.
realName
chosen
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
-
C.
titleCharacterRealName
Indicates that a character known by a title or alias has the specified real (personal) name.
-
D.
eraInCanon
Indicates that a subject belongs to, occurs within, or is classified as part of a specific era defined in a canon or fictional continuity.
-
E.
protagonistRealWorldName
Indicates that a character’s name in the real world (outside a fictional, virtual, or alternate setting) is associated with that character as the story’s protagonist.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.