Triple
T32526245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superflu |
E831321
|
entity |
| Predicate | associatedCharacterGroup |
P47706
|
FINISHED |
| Object | survivors immune to the virus |
—
|
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: survivors immune to the virus | Statement: [Superflu, associatedCharacterGroup, survivors immune to the virus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCharacterGroup Context triple: [Superflu, associatedCharacterGroup, survivors immune to the virus]
-
A.
associatedWithCharacterGroup
chosen
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
B.
associatedWithCharacterFamily
Indicates a relationship where something is linked or connected to a particular character’s family.
-
C.
titleCharacterGroup
Indicates that a group of characters is associated with or featured in the title of a work.
-
D.
belongsToCharacter
Indicates that something is owned, associated with, or under the domain of a particular character.
-
E.
introducesCharacterGroup
Indicates that an entity presents or brings a group of characters into the narrative or context for the first time.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:01 a.m.