Triple
T4917950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eteocles |
E110392
|
entity |
| Predicate | oathOrAgreement |
P1202
|
FINISHED |
| Object | pact with Polynices to alternate rule of Thebes |
—
|
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: pact with Polynices to alternate rule of Thebes | Statement: [Eteocles, oathOrAgreement, pact with Polynices to alternate rule of Thebes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oathOrAgreement Context triple: [Eteocles, oathOrAgreement, pact with Polynices to alternate rule of Thebes]
-
A.
oath
chosen
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.
-
B.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
C.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
D.
aimOfAgreement
Indicates the intended purpose or objective that an agreement is designed to achieve.
-
E.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6fa760448190946401b4b21ea8b7 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.