Triple
T38116833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sgt. Fury and his Howling Commandos #8 |
E951812
|
entity |
| Predicate | hasIssueNumber |
P86565
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Sgt. Fury and his Howling Commandos #8, hasIssueNumber, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIssueNumber Context triple: [Sgt. Fury and his Howling Commandos #8, hasIssueNumber, 8]
-
A.
hasIssueNumbering
Indicates that an item, such as a publication or series, is assigned a specific issue number or follows a defined issue numbering scheme.
-
B.
issueNumber
chosen
Indicates the specific numeric identifier assigned to distinguish one issue from others within a series or collection.
-
C.
hasIssueWith
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
D.
numberOfIssues
Indicates the quantity of issues associated with a given entity or context.
-
E.
hasTargetIssue
Indicates that an entity is associated with or directed toward a specific issue, problem, or concern as its focus.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.