Triple
T8460661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biainili |
E200029
|
entity |
| Predicate | usedTitleForKing |
P78349
|
FINISHED |
| Object | king of Biainili |
—
|
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: king of Biainili | Statement: [Biainili, usedTitleForKing, king of Biainili]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTitleForKing Context triple: [Biainili, usedTitleForKing, king of Biainili]
-
A.
reignTitleUsedTo
Indicates that a particular reign title was previously used to refer to or designate a given ruler, period, or authority.
-
B.
usesRoyalTitle
chosen
Indicates that one entity refers to another using a royal title or honorific (such as king, queen, prince, or similar).
-
C.
usedTitleIn
Indicates that one entity employed or referenced another entity as a title in some context.
-
D.
redefinedMonarchTitleFrom
Indicates that a monarch’s official title has been changed or updated from a previous form specified by the related entity.
-
E.
royalTitularyFeature
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe49fca788190a8728ff74f4d26f5 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.