Triple
T4956401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polynices |
E111290
|
entity |
| Predicate | agreedTo |
P611
|
FINISHED |
| Object | alternating rule of Thebes with Eteocles |
—
|
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: alternating rule of Thebes with Eteocles | Statement: [Polynices, agreedTo, alternating rule of Thebes with Eteocles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agreedTo Context triple: [Polynices, agreedTo, alternating rule of Thebes with Eteocles]
-
A.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
B.
agreement
chosen
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
C.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
-
D.
basedOnAgreementWith
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
-
E.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71d6ba9c8190932f8d81240c3f56 |
completed | March 20, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3beb008190852fd6150813b252 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:32 p.m.