Triple
T33727879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cards as Weapons |
E864192
|
entity |
| Predicate | outOfPrintStatus |
P33833
|
FINISHED |
| Object | often reported as difficult to find |
—
|
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: often reported as difficult to find | Statement: [Cards as Weapons, outOfPrintStatus, often reported as difficult to find]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outOfPrintStatus Context triple: [Cards as Weapons, outOfPrintStatus, often reported as difficult to find]
-
A.
printingStatus
Indicates the current state or progress of a printing process for an item or document.
-
B.
hasImprintStatus
chosen
Indicates that an entity has a particular imprint-related status or condition assigned to it.
-
C.
printingPressClosedIn
Indicates that a printing press ceased operations or was shut down in a specified location.
-
D.
authorRequestedOutOfPrint
Indicates that the author has formally requested that the work be taken out of print and no longer actively produced or distributed.
-
E.
printedBy
Indicates that one entity is produced or output in physical or digital form by another entity acting as the printer or printing agent.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb1b91bc8190a40733039fe939b3 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:44 a.m.