Triple
T29709806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aalwar |
E751746
|
entity |
| Predicate | featuresVigilanteProtagonist |
P21469
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aalwar, featuresVigilanteProtagonist, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresVigilanteProtagonist Context triple: [Aalwar, featuresVigilanteProtagonist, true]
-
A.
isVigilante
Indicates that an entity takes the law into their own hands, acting outside official authority to pursue or punish perceived wrongdoers.
-
B.
featuresProtagonistOccupation
Indicates that the work’s main character has a specified occupation or job role.
-
C.
featuresAntagonistEntity
Indicates that the subject includes or involves an entity serving as an antagonist in the context of a narrative, interaction, or scenario.
-
D.
protagonistCharacteristic
chosen
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
E.
featuresVillainActor
Indicates that the subject includes or presents an actor in the role of a villain.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
Created at: April 28, 2026, 7:30 p.m.