Triple
T23896257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archie Comics |
E600909
|
entity |
| Predicate | publishesCharacter |
P153977
|
FINISHED |
| Object | Sabrina Spellman |
—
|
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: Sabrina Spellman | Statement: [Archie Comics, publishesCharacter, Sabrina Spellman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishesCharacter Context triple: [Archie Comics, publishesCharacter, Sabrina Spellman]
-
A.
introducesFictionalCharacter
Indicates that one entity is responsible for first presenting or bringing a fictional character into a narrative work or story.
-
B.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
C.
writtenForCharacter
Indicates that a piece of writing (such as a script, scene, or dialogue) was specifically created or tailored for a particular character.
-
D.
commissionedCharacterName
Indicates that an entity has been given or assigned a specific character name as part of a commission or commissioned work.
-
E.
characterAcquisition
Indicates the relationship in which an entity comes to possess, gain, or obtain a character, trait, or attribute.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdda39448190bdefa953e0558583 |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 8:25 p.m.