Triple
T15373982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jianshen |
E367619
|
entity |
| Predicate | associatedReignPeriodStart |
P62322
|
FINISHED |
| Object | 1464 |
—
|
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: 1464 | Statement: [Jianshen, associatedReignPeriodStart, 1464]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedReignPeriodStart Context triple: [Jianshen, associatedReignPeriodStart, 1464]
-
A.
associatedWithHistoricalFigureReignStart
chosen
Indicates a relationship where something is linked to the beginning of a specific historical figure’s reign.
-
B.
ended reign start year
Indicates the calendar year in which a ruler’s period of reign came to an end.
-
C.
reignedFrom
Indicates the time period during which an entity held ruling authority or sovereignty over a domain.
-
D.
originatedInReignOf
Indicates that something began, was initiated, or first came into existence during the rule or governing period of a particular ruler or authority.
-
E.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5d6f808190b0a4cdb35dc89e69 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:18 a.m.