Triple
T30849633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avengers: X-Sanction |
E785741
|
entity |
| Predicate | targetedTeamMembers |
P129160
|
FINISHED |
| Object | Captain America |
—
|
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: Captain America | Statement: [Avengers: X-Sanction, targetedTeamMembers, Captain America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedTeamMembers Context triple: [Avengers: X-Sanction, targetedTeamMembers, Captain America]
-
A.
managedTeamFrom
Indicates that one entity led, directed, or supervised a team originating from or based in another specified entity.
-
B.
associatedWithTeamMember
chosen
Indicates a relationship where an entity has a connection, involvement, or linkage with a specific member of a team.
-
C.
organizedTeam
Indicates that an entity has formed, structured, or coordinated a group of individuals to function together as a team.
-
D.
associatedTeamPrincipal
Indicates that there is a relationship in which a specific team principal is linked or connected to a particular team.
-
E.
includesTeamsThat
Indicates that an entity contains or encompasses specific teams as part of its composition or scope.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 29, 2026, 8:46 p.m.