Triple
T32022987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anbay |
E817743
|
entity |
| Predicate | oathFormulaUsage |
P48431
|
FINISHED |
| Object | invoked as divine witness |
—
|
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: invoked as divine witness | Statement: [Anbay, oathFormulaUsage, invoked as divine witness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oathFormulaUsage Context triple: [Anbay, oathFormulaUsage, invoked as divine witness]
-
A.
oathName
Indicates the specific name or title assigned to an oath in the relationship.
-
B.
oath
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
-
C.
oathsAbout
Indicates that one entity makes or concerns a formal oath regarding another entity or subject.
-
D.
titleUsedInOaths
chosen
Indicates that a particular title is formally invoked or referenced within oaths or sworn declarations.
-
E.
oathByStyx
Indicates a relationship where an oath or solemn vow is sworn invoking the River Styx as the binding, unbreakable guarantor of the promise.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4684000819090d1f2f28af40db9 |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:17 a.m.