Triple
T29149425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fightin' 5 #40 |
E738861
|
entity |
| Predicate | hasVigilanteCharacter |
P112256
|
FINISHED |
| Object | Peacemaker |
—
|
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: Peacemaker | Statement: [Fightin' 5 #40, hasVigilanteCharacter, Peacemaker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVigilanteCharacter Context triple: [Fightin' 5 #40, hasVigilanteCharacter, Peacemaker]
-
A.
isVigilante
chosen
Indicates that an entity takes the law into their own hands, acting outside official authority to pursue or punish perceived wrongdoers.
-
B.
hasVigilanteTheme
Indicates that the subject involves or centers around vigilante justice, where individuals take the law into their own hands outside official legal authority.
-
C.
hasVillain
Indicates that one entity is the villain or primary antagonist associated with another entity.
-
D.
hasSuperheroMantle
Indicates that one entity holds or has assumed the superhero identity, title, or role associated with another entity.
-
E.
hasEnforcerCharacter
Indicates that an entity includes or is associated with a character who acts as an enforcer, carrying out enforcement or coercive roles 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 28, 2026, 11:41 a.m.