Triple
T8006903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zizhi Tongjian |
E186383
|
entity |
| Predicate | compilationDuration |
P17474
|
FINISHED |
| Object | about 19 years |
—
|
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 19 years | Statement: [Zizhi Tongjian, compilationDuration, about 19 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compilationDuration Context triple: [Zizhi Tongjian, compilationDuration, about 19 years]
-
A.
compilationStatus
Indicates the current state or outcome of a compilation process for a given entity (e.g., whether it is pending, in progress, successful, or failed).
-
B.
compilationType
Indicates the specific method or mode by which something is compiled or assembled into a final form.
-
C.
compiledAt
Indicates that one entity was built or transformed into an executable or final form at a specific time or location represented by the other entity.
-
D.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
-
E.
timeToComplete
chosen
Indicates the duration required for an entity or process to be fully completed.
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf8a6048190970685a83fd2f59d |
completed | March 31, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:18 p.m.