Triple
T7947698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Records of the Three Kingdoms |
E184536
|
entity |
| Predicate | historicalScopeStart |
P76219
|
FINISHED |
| Object | late 2nd century |
—
|
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: late 2nd century | Statement: [Records of the Three Kingdoms, historicalScopeStart, late 2nd century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalScopeStart Context triple: [Records of the Three Kingdoms, historicalScopeStart, late 2nd century]
-
A.
chronologyStart
chosen
Indicates the point in time at which a sequence, event, or temporal record begins.
-
B.
historicalClassificationStart
Indicates the point in time when a particular historical classification or categorization of an entity begins to apply.
-
C.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
D.
historicSignificanceScope
Indicates the extent or level (e.g., local, national, global) at which something is considered historically significant.
-
E.
historicallyEncompassed
Indicates that one entity previously included, covered, or contained another entity within its scope, extent, or boundaries during a past historical 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b2abdbc819085ae53826d36af3b |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae9361bc48190886b7681e563d46b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.