Triple
T36879781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lone Avenger |
E911444
|
entity |
| Predicate | hasHeroCharacterType |
P185186
|
FINISHED |
| Object | masked hero |
—
|
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: masked hero | Statement: [The Lone Avenger, hasHeroCharacterType, masked hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeroCharacterType Context triple: [The Lone Avenger, hasHeroCharacterType, masked hero]
-
A.
hasCharacterAbilityType
Indicates that an entity possesses a specific type or category of character ability.
-
B.
hasPlayableCharacter
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
C.
heldByCharacterType
Indicates that something (such as an item, role, or status) is possessed or carried by a character of a specified type.
-
D.
hasProtagonistClass
chosen
Indicates that a work’s main character belongs to a specified class or category.
-
E.
hasHeroicResponder
Indicates that an entity is associated with or supported by another entity that performs a heroic or emergency response action on its behalf.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 3, 2026, 4:13 p.m.