Triple
T30935287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strange Tales |
E788104
|
entity |
| Predicate | hasIssueNumbering |
P174095
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Strange Tales, hasIssueNumbering, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIssueNumbering Context triple: [Strange Tales, hasIssueNumbering, yes]
-
A.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
B.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
C.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
D.
hasCategoryNumbering
Indicates that an entity is assigned or associated with a specific category-based numbering or index within a classification system.
-
E.
issueNumberingIncludesSpecialNumber
Indicates that the numbering system used for issues includes at least one designated special or non-standard number.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: April 29, 2026, 8:52 p.m.