Triple
T17779321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camera Work |
E443854
|
entity |
| Predicate | issueNumberingIncludesSpecialNumber |
P128897
|
FINISHED |
| Object | 49-50 |
—
|
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: 49-50 | Statement: [Camera Work, issueNumberingIncludesSpecialNumber, 49-50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issueNumberingIncludesSpecialNumber Context triple: [Camera Work, issueNumberingIncludesSpecialNumber, 49-50]
-
A.
issueNumber
Indicates the specific numeric identifier assigned to distinguish one issue from others within a series or collection.
-
B.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
C.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
D.
numberingReason
Indicates the rationale or basis for assigning a particular number or numbering scheme to something.
-
E.
firstIssueNumber
Indicates the issue number at which something (such as a series, feature, or character) first appeared or began.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48720734c819085ebe37065b8c8f3 |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:12 a.m.