Triple
T31390625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superhero Movie |
E800720
|
entity |
| Predicate | mainCharacterIs |
P97041
|
FINISHED |
| Object | teenage superhero |
—
|
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: teenage superhero | Statement: [Superhero Movie, mainCharacterIs, teenage superhero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterIs Context triple: [Superhero Movie, mainCharacterIs, teenage superhero]
-
A.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
B.
mainCharacterField
Indicates that one entity is designated as the primary or central character associated with another entity, such as a work or narrative.
-
C.
mainMortalCharacter
Indicates that the referenced entity serves as the primary mortal (non-immortal) character in the context of a story or narrative.
-
D.
mainCharactersAre
Indicates that the specified entities serve as the primary or central characters in a narrative or work.
-
E.
hasPrimaryCharacter
chosen
Indicates that an entity features another entity as its main or central character.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 29, 2026, 9:19 p.m.