Triple
T35316914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avengers: Ultron Unlimited |
E1019928
|
entity |
| Predicate | spansIssues |
P129130
|
FINISHED |
| Object | Avengers (vol. 3) #19 |
—
|
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: Avengers (vol. 3) #19 | Statement: [Avengers: Ultron Unlimited, spansIssues, Avengers (vol. 3) #19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spansIssues Context triple: [Avengers: Ultron Unlimited, spansIssues, Avengers (vol. 3) #19]
-
A.
involvesIssue
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
B.
containsIssue
chosen
Indicates that one entity includes, encompasses, or has within it a particular issue, problem, or defect.
-
C.
issueIncludes
Indicates that an issue or problem encompasses, contains, or involves a specified element, component, or sub-issue as part of its scope.
-
D.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
E.
issuesMark
Indicates that one entity assigns or gives a mark, grade, or score to another entity.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f790929a888190aa7084a792c304fc |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.