Triple
T37716195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Avengers Presents (2008) limited series |
E939457
|
entity |
| Predicate | issueFormat |
P130
|
FINISHED |
| Object | monthly single issues |
—
|
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: monthly single issues | Statement: [Young Avengers Presents (2008) limited series, issueFormat, monthly single issues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issueFormat Context triple: [Young Avengers Presents (2008) limited series, issueFormat, monthly single issues]
-
A.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
B.
issueFramedAs
Indicates that one party presents or characterizes an issue in a particular way or perspective to another party or audience.
-
C.
issue
Indicates that an entity formally publishes, releases, or distributes something, such as a document, statement, or item, often in an official or authoritative capacity.
-
D.
issuesMark
Indicates that one entity assigns or gives a mark, grade, or score to another entity.
-
E.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.