Triple
T14486784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongle Encyclopedia |
E359248
|
entity |
| Predicate | extantVolumesApproximate |
P2734
|
FINISHED |
| Object | about 400 volumes |
—
|
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: about 400 volumes | Statement: [Yongle Encyclopedia, extantVolumesApproximate, about 400 volumes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extantVolumesApproximate Context triple: [Yongle Encyclopedia, extantVolumesApproximate, about 400 volumes]
-
A.
numberOfVolumes
chosen
Indicates the total count of separate volumes or parts that make up a multi-volume work or collection.
-
B.
collectionVolume
Indicates the total physical or spatial amount occupied by a collection, such as its size, capacity, or volume.
-
C.
volumeOf
Indicates the quantitative three-dimensional space occupied by an entity or contained within an object.
-
D.
approximateVolumeInCubicCentimetres
Indicates that one entity has an estimated or roughly calculated volume measured in cubic centimetres.
-
E.
hasApproximateVellumCopies
Indicates that one entity possesses or is associated with a number of vellum copies that is approximate rather than exact.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924ee0f08190baf68318b41fa64d |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.