Triple
T29942153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Age of Ultron (comics event) |
E760526
|
entity |
| Predicate | hasMainSeriesIssueCount |
P129298
|
FINISHED |
| Object | 10 |
—
|
LITERAL 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: 10 | Statement: [Age of Ultron (comics event), hasMainSeriesIssueCount, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainSeriesIssueCount Context triple: [Age of Ultron (comics event), hasMainSeriesIssueCount, 10]
-
A.
mainSeriesIssueCount
chosen
Indicates the total number of issues contained in the primary or main series associated with an entity.
-
B.
hasMainSeriesEntry
Indicates that an entity is a primary or canonical installment within a larger series or sequence of related works.
-
C.
hasIssueNumbering
Indicates that an item, such as a publication or series, is assigned a specific issue number or follows a defined issue numbering scheme.
-
D.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
E.
soloSeriesIssueCount
Indicates the number of issues released in an entity’s solo series.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: April 29, 2026, 6:23 p.m.