Triple
T38018112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taishō Shinshū Daizōkyō |
E948549
|
entity |
| Predicate | includesSupplementVolumes |
P20051
|
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: [Taishō Shinshū Daizōkyō, includesSupplementVolumes, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSupplementVolumes Context triple: [Taishō Shinshū Daizōkyō, includesSupplementVolumes, yes]
-
A.
hasSupplement
chosen
Indicates that one entity provides or is associated with an additional supporting or enhancing item, resource, or component for another entity.
-
B.
seriesIncludes
Indicates that a particular series contains or encompasses the referenced item as one of its constituent parts.
-
C.
includesCompanion
Indicates that one entity involves, contains, or is accompanied by another entity acting as a companion.
-
D.
collectionAlsoIncludes
Indicates that a collection contains, in addition to some already-specified items, one or more further items that are also part of that same collection.
-
E.
supportsCustomCovers
Indicates that one entity provides the capability for another entity to use or define custom cover designs or images.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.