Triple
T1981803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Kings |
E43042
|
entity |
| Predicate | indicatesAuthorityOver |
P35765
|
FINISHED |
| Object | earthly rulers |
—
|
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: earthly rulers | Statement: [King of Kings, indicatesAuthorityOver, earthly rulers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesAuthorityOver Context triple: [King of Kings, indicatesAuthorityOver, earthly rulers]
-
A.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
-
B.
legalAuthorityOver
Indicates that one entity has the recognized power or right to make, enforce, or adjudicate rules or decisions concerning another entity.
-
C.
hasLegalAuthorityFrom
Indicates that one entity possesses formal legal power, rights, or authorization that originates from or is granted by another entity.
-
D.
designatesAuthority
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
-
E.
reaffirmsAuthorityOf
Indicates that one entity confirms, strengthens, or restates the legitimacy or power of another entity’s authority.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb96f932881908bebfc4176fda7c0 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb798d288819083132cf14605bd02 |
completed | March 7, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69abb96e07c08190beed60096e9d71b4 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:37 p.m.