Triple
T8045797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sima Guang |
E187546
|
entity |
| Predicate | zizhiTongjianCoverageStartYear |
P9200
|
FINISHED |
| Object | 403 BC |
—
|
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: 403 BC | Statement: [Sima Guang, zizhiTongjianCoverageStartYear, 403 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zizhiTongjianCoverageStartYear Context triple: [Sima Guang, zizhiTongjianCoverageStartYear, 403 BC]
-
A.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
-
B.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
C.
initialCoverage
Indicates that an entity provides or is subject to the first or starting level of coverage within a broader coverage arrangement or period.
-
D.
contractStartYear
Indicates the calendar year in which a contract between parties officially begins.
-
E.
coversPeriodStart
chosen
Indicates that the time span or coverage of one entity begins at, or includes, the specified starting point in time of another entity or period.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f4d9ddc8190a7dcf85ed47ee6c3 |
completed | March 31, 2026, 3:28 a.m. |
| PD | Predicate disambiguation | batch_69cb049688208190b32088bd2c5930bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:24 p.m.