Triple
T35849963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rape of Tamar |
E1036320
|
entity |
| Predicate | hasAvenger |
P183899
|
FINISHED |
| Object | Absalom |
—
|
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: Absalom | Statement: [Rape of Tamar, hasAvenger, Absalom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAvenger Context triple: [Rape of Tamar, hasAvenger, Absalom]
-
A.
roleInAvengers
Indicates that an entity has a specific role or membership status within the Avengers team.
-
B.
avenges
Indicates that one entity retaliates or exacts retribution against another entity on behalf of a wrong or harm done to a third party.
-
C.
hasSuperheroMantle
Indicates that one entity holds or has assumed the superhero identity, title, or role associated with another entity.
-
D.
marvelCinematicUniverseDebutFilm
Indicates the film in which an entity (such as a character or actor) first appeared within the Marvel Cinematic Universe.
-
E.
hasEponymousHero
Indicates that a work or narrative features a hero whose name is the same as, or gives its name to, the work itself.
- F. None of above. chosen
Provenance (4 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_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa33e0488190a135166bb67e1118 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.