Triple
T898917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apocrypha (in early editions) |
E19403
|
entity |
| Predicate | hasPrintFeature |
P21150
|
FINISHED |
| Object | printed as a separate section |
—
|
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: printed as a separate section | Statement: [Apocrypha (in early editions), hasPrintFeature, printed as a separate section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrintFeature Context triple: [Apocrypha (in early editions), hasPrintFeature, printed as a separate section]
-
A.
hasPrintVersion
Indicates that one entity exists or is available as a printed or physical edition of another entity.
-
B.
printingMethod
Indicates the technique or process used to produce a printed item or image.
-
C.
printedOn
Indicates that something is produced or reproduced in physical form on a specified material, surface, or medium.
-
D.
printedBy
Indicates that one entity is produced or output in physical or digital form by another entity acting as the printer or printing agent.
-
E.
hasImprintType
Indicates that an entity (such as a publication or product) is associated with a specific type or category of imprint.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad4162848190aa2787b2fa3e6575 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa979d408190b17ccfde132ea628 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4abb157d08190a7d7281eb3f1b788 |
completed | March 1, 2026, 9:12 p.m. |
Created at: March 1, 2026, 7:39 p.m.