Triple
T10078367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamitsumaki |
E213831
|
entity |
| Predicate | hasThreeVolumeStructureRole |
P91960
|
FINISHED |
| Object | first volume |
—
|
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: first volume | Statement: [Kamitsumaki, hasThreeVolumeStructureRole, first volume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThreeVolumeStructureRole Context triple: [Kamitsumaki, hasThreeVolumeStructureRole, first volume]
-
A.
numberOfVolumes
Indicates the total count of separate volumes or parts that make up a multi-volume work or collection.
-
B.
hasLargeVolume
Indicates that an entity possesses or is characterized by a comparatively large physical or quantitative volume.
-
C.
hasThreeBooksWith
Indicates that two entities are related by one having exactly three books together with the other (e.g., jointly owned, shared, or associated as a group of three books).
-
D.
tripleLayerCapacity
Indicates that something has the capacity or capability to function in or support three distinct layers or levels simultaneously.
-
E.
has3DModels
Indicates that an entity is associated with one or more three-dimensional (3D) digital models representing it.
- 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_69ca839bf730819086900c323c9b8c95 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd030a0fc819084b523e8e63636fa |
completed | April 2, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9 p.m.