Triple
T14344347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Maiden |
E355674
|
entity |
| Predicate | bearerReignEnd |
P2721
|
FINISHED |
| Object | 1165 |
—
|
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: 1165 | Statement: [the Maiden, bearerReignEnd, 1165]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerReignEnd Context triple: [the Maiden, bearerReignEnd, 1165]
-
A.
reignClaimedEnd
Indicates the point in time or event at which a previously asserted or claimed reign or rule is considered to have ended.
-
B.
endOfReign
chosen
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
C.
reignAsHeirApparentEnd
Indicates the point in time or event at which an individual’s period of serving as heir apparent to a throne or title comes to an end.
-
D.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
E.
bearerFounded
Indicates that the bearer (such as a person or organization) is the one who established or created the associated entity (such as a company, institution, or project).
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e89ed9c8190acdb647ee618e919 |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.