Triple
T31953352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Captain America |
E815839
|
entity |
| Predicate | includesFormerAvenger |
P108484
|
FINISHED |
| Object | Clint Barton |
E953256
|
NE 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: Clint Barton | Statement: [Team Captain America, includesFormerAvenger, Clint Barton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFormerAvenger Context triple: [Team Captain America, includesFormerAvenger, Clint Barton]
-
A.
hasAvenger
Indicates that an entity is associated with or possesses an Avenger as part of its members, attributes, or related characters.
-
B.
roleInAvengers
chosen
Indicates that an entity has a specific role or membership status within the Avengers team.
-
C.
roleInAvengersInfinityWar
Indicates that an entity has a specific role or appearance in the movie "Avengers: Infinity War."
-
D.
roleInMarvelLore
Indicates the specific function, status, or narrative significance an entity holds within the Marvel universe’s storyline and mythology.
-
E.
avenges
Indicates that one entity retaliates or exacts retribution against another entity on behalf of a wrong or harm done to a third party.
- F. None of above.
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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01a0b63d148190b10206509c0a0a5b |
completed | May 11, 2026, 9:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eb14034e0819088f0cbbb5b77d160 |
completed | June 14, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_6a01a0245d4c8190a3c3fbbe83f0389d |
completed | May 11, 2026, 9:23 a.m. |
Created at: May 1, 2026, 12:08 a.m.