Triple
T36687563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krishna I |
E905861
|
entity |
| Predicate | usedRoyalTitlesInInscriptions |
P178278
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Krishna I, usedRoyalTitlesInInscriptions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRoyalTitlesInInscriptions Context triple: [Krishna I, usedRoyalTitlesInInscriptions, true]
-
A.
usesRoyalTitle
Indicates that one entity refers to another using a royal title or honorific (such as king, queen, prince, or similar).
-
B.
usedAsRoyalNameOn
chosen
Indicates that something served as a royal name or title during a specified time or in a specified context.
-
C.
traditionalTitleOfKing
Indicates that the object is the customary or historically recognized royal title held by the king specified as the subject.
-
D.
ancientTitle
Indicates that an entity holds or is associated with a title or designation originating from ancient times.
-
E.
usedRoyalSerekh
Indicates that one entity employed or displayed the royal serekh (a pharaonic name emblem) associated with another entity.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7c5dc0081908f0e289286853c3d |
completed | May 3, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.