Triple
T16731446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siku Quanshu |
E406601
|
entity |
| Predicate | startOfCompilation |
P97158
|
FINISHED |
| Object | 1772 |
—
|
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: 1772 | Statement: [Siku Quanshu, startOfCompilation, 1772]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfCompilation Context triple: [Siku Quanshu, startOfCompilation, 1772]
-
A.
compilation
Indicates the process or result of collecting and assembling various items, works, or elements into a single organized whole.
-
B.
timeOfCompilationContext
chosen
Indicates the specific time or temporal context in which a compilation process or compilation-related event occurs.
-
C.
compilationContext
Indicates the situational or environmental conditions under which something is compiled, such as the tools, settings, or parameters used during the compilation process.
-
D.
isOnCompilation
Indicates that one entity (typically a work or item) is included as part of a compilation or collection.
-
E.
compilationType
Indicates the specific method or mode by which something is compiled or assembled into a final form.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c362bb88190921fab43d76c3ee8 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.