Triple
T6413923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adonijah |
E127774
|
entity |
| Predicate | requestInterpretedAs |
P67724
|
FINISHED |
| Object | renewed claim to the throne |
—
|
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: renewed claim to the throne | Statement: [Adonijah, requestInterpretedAs, renewed claim to the throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestInterpretedAs Context triple: [Adonijah, requestInterpretedAs, renewed claim to the throne]
-
A.
requestedFrom
Indicates that one entity has made a request to another entity as the source or provider of something.
-
B.
requiresInterpretationInLightOf
Indicates that something must be understood, evaluated, or applied by considering it in the context or framework provided by another thing.
-
C.
intendedInterpretation
chosen
Indicates that one entity is meant to be understood or interpreted in a particular way, sense, or meaning relative to another.
-
D.
interpretedAs
Indicates that something is understood, perceived, or taken to mean something else, often based on context or subjective judgment.
-
E.
eraInterpreted
Indicates that one entity has been interpreted, understood, or given meaning by 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068e5187c8190a6be1b934e0f1b3a |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:42 p.m.