Triple
T37109236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porcupine |
E918937
|
entity |
| Predicate | hasProtagonistNickname |
—
|
GENERATED |
| Object | Jack |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistNickname Context triple: [Porcupine, hasProtagonistNickname, Jack]
-
A.
leadCharacterNickname
Indicates that one entity is the nickname commonly used for the lead (main) character of another entity.
-
B.
protagonistAlsoKnownAs
chosen
Indicates that an entity serving as a protagonist is alternatively referred to by another name or alias.
-
C.
propNickname
Indicates that one entity is used as a nickname or informal alternative name for another entity.
-
D.
usesRecurringProtagonistName
Indicates that a work repeatedly features the same protagonist character under a consistent name across multiple installments or stories.
-
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 (1 batch)
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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.