Triple
T29085932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gojong |
E734112
|
entity |
| Predicate | emperorReignEnd |
P35129
|
FINISHED |
| Object | 1907 |
—
|
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: 1907 | Statement: [Gojong, emperorReignEnd, 1907]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emperorReignEnd Context triple: [Gojong, emperorReignEnd, 1907]
-
A.
lastEmperorReignEnd
Indicates the date or time at which the reign of the last emperor of a given realm or dynasty ended.
-
B.
imperialPeriodEnd
Indicates the point in time or event at which an imperial period or era comes to an end.
-
C.
endEmperor
chosen
Indicates the point or event at which an individual's tenure or status as emperor comes to an end.
-
D.
coEmperorEnd
Indicates that one entity’s tenure as co-emperor with another entity comes to an end at a specific point in time.
-
E.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6614707088190bce270d4392e8429 |
completed | May 2, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11 a.m.