Triple
T20337636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings of Armenia |
E495656
|
entity |
| Predicate | lastHolderDiedIn |
P139745
|
FINISHED |
| Object | 1393 |
—
|
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: 1393 | Statement: [Kings of Armenia, lastHolderDiedIn, 1393]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastHolderDiedIn Context triple: [Kings of Armenia, lastHolderDiedIn, 1393]
-
A.
lastHolder
Indicates that the subject is the most recent entity to have possessed, owned, or held the object.
-
B.
diedAfter
Indicates that one entity’s death occurred later in time than another entity’s death.
-
C.
lastCultivatedIndividualDied
Indicates that the most recently cultivated individual of a given entity has died.
-
D.
secondHolderDeathYear
Indicates the calendar year in which the second holder of something (such as a title, position, or asset) died.
-
E.
firstHolderDeathDate
Indicates the date on which the initial or original holder of something (such as a title, account, or asset) died.
- F. None of above. chosen
Provenance (4 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677ed75e081909bfc534033ac1c59 |
completed | April 20, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:23 a.m.