Triple
T19133671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Styx |
E468378
|
entity |
| Predicate | roleInOaths |
P134547
|
FINISHED |
| Object | guarantor of divine oaths |
—
|
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: guarantor of divine oaths | Statement: [Styx, roleInOaths, guarantor of divine oaths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInOaths Context triple: [Styx, roleInOaths, guarantor of divine oaths]
-
A.
oathTakenBy
Indicates that an oath or formal promise has been made by a specific entity.
-
B.
religionInOath
Indicates that a religious element, such as a deity, scripture, or religious principle, is invoked or referenced within an oath or sworn statement.
-
C.
oathsAbout
Indicates that one entity makes or concerns a formal oath regarding another entity or subject.
-
D.
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.
-
E.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3eb325081909035beefd1c9daf0 |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:05 p.m.