Triple
T5181737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kayser-i Rûm |
E116936
|
entity |
| Predicate | titleHolderClaim |
P5052
|
FINISHED |
| Object | universal rulership |
—
|
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: universal rulership | Statement: [Kayser-i Rûm, titleHolderClaim, universal rulership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderClaim Context triple: [Kayser-i Rûm, titleHolderClaim, universal rulership]
-
A.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
B.
claimedTitle
chosen
Indicates that an entity asserts or declares possession of a particular title or rank.
-
C.
titleHolderHouse
Indicates that a particular house or noble family holds or is associated with a specific title.
-
D.
titleHolderIsUsually
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
-
E.
titleHolderUnder
Indicates that one entity holds a title, position, or rank under the authority, jurisdiction, or hierarchy of 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd799bc58c819098a8e91e21baaef4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.