Triple
T28244042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Kingdoms |
E712111
|
entity |
| Predicate | timeInHistoryOfTopic |
P12795
|
FINISHED |
| Object | Chinese history |
—
|
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: Chinese history | Statement: [Three Kingdoms, timeInHistoryOfTopic, Chinese history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInHistoryOfTopic Context triple: [Three Kingdoms, timeInHistoryOfTopic, Chinese history]
-
A.
historicallyDiscussedBy
Indicates that the subject has been a topic of discussion, analysis, or commentary by the specified person or group in a historical context.
-
B.
historicalConceptEmergence
Indicates the point or process by which a historical concept first appears, develops, or becomes recognized within a particular temporal or cultural context.
-
C.
timeExistence
chosen
Indicates the period or duration during which an entity exists or is valid.
-
D.
timePeriodOfRiseInPopularity
Indicates the time span during which something became increasingly popular or widely favored.
-
E.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643c77edc8190bb23727297adb769 |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11 p.m.