Triple
T4056119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Folio of Shakespeare |
E84697
|
entity |
| Predicate | hasPhysicalMedium |
P53051
|
FINISHED |
| Object | paper |
—
|
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: paper | Statement: [First Folio of Shakespeare, hasPhysicalMedium, paper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalMedium Context triple: [First Folio of Shakespeare, hasPhysicalMedium, paper]
-
A.
hasAssociatedMedium
Indicates that one entity is linked to another entity that serves as its medium, format, or channel of expression or transmission.
-
B.
notableRecordingMedium
Indicates that an entity is notably recorded, documented, or expressed using a particular medium or format.
-
C.
hasDigitalForm
Indicates that something exists or is available in a digital or electronic format.
-
D.
hasHomeMediaRelease
Indicates that a work has been released in a home media format (such as DVD, Blu-ray, or digital home release).
-
E.
physicalReleaseCharacteristic
Indicates a characteristic or property that describes some physical aspect or quality of a release (such as a product, media, or publication) in relation to that release.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbabec608190a35d39d3d03b928b |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef9fcb31c819098d5287b6fc84f4e |
completed | March 9, 2026, 4:49 p.m. |
Created at: March 9, 2026, 3:38 p.m.