Triple
T33954499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Season of Infamy |
E870528
|
entity |
| Predicate | addsContentForCharacter |
P120998
|
FINISHED |
| Object | Batman |
—
|
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: Batman | Statement: [Season of Infamy, addsContentForCharacter, Batman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsContentForCharacter Context triple: [Season of Infamy, addsContentForCharacter, Batman]
-
A.
providesAdditionalCharactersFor
Indicates that one entity supplies extra or supplementary characters to be used by another entity or process.
-
B.
implementationCharacter
Indicates that one entity specifies or defines a particular characteristic, feature, or property of the implementation of another entity.
-
C.
publishesCharacter
Indicates that an entity (such as a publisher or platform) makes a character publicly available or officially releases that character.
-
D.
createsContentFor
chosen
Indicates that one entity produces or generates content intended to be used by or directed toward another entity.
-
E.
appliesToCharacter
Indicates that an action, rule, or property is specifically directed toward or relevant for a particular 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.