Triple
T9114383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strange Tales #110 |
E218687
|
entity |
| Predicate | issueNumber |
P86565
|
FINISHED |
| Object | 110 |
—
|
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: 110 | Statement: [Strange Tales #110, issueNumber, 110]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issueNumber Context triple: [Strange Tales #110, issueNumber, 110]
-
A.
numberOfIssues
Indicates the quantity of issues associated with a given entity or context.
-
B.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
C.
issuesTitle
Indicates that an entity formally grants or assigns an official title or designation to another entity.
-
D.
firstIssueNumber
Indicates the issue number at which something (such as a series, feature, or character) first appeared or began.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca84c209c8190b082a9b8499bedf7 |
completed | April 1, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc66d7bf648190b8bff5b584b84975 |
completed | April 1, 2026, 12:29 a.m. |
Created at: March 30, 2026, 7:16 p.m.