Triple
T1981824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Kings |
E43042
|
entity |
| Predicate | usedToAffirm |
P3106
|
FINISHED |
| Object | God's superiority over political powers |
—
|
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: God's superiority over political powers | Statement: [King of Kings, usedToAffirm, God's superiority over political powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToAffirm Context triple: [King of Kings, usedToAffirm, God's superiority over political powers]
-
A.
affirms
chosen
Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
-
B.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
C.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
D.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
E.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, 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_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. |
Created at: March 4, 2026, 7:37 p.m.