Triple
T30168026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartan kings |
E766846
|
entity |
| Predicate | couldBeDeposedFor |
P147949
|
FINISHED |
| Object | misconduct |
—
|
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: misconduct | Statement: [Spartan kings, couldBeDeposedFor, misconduct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldBeDeposedFor Context triple: [Spartan kings, couldBeDeposedFor, misconduct]
-
A.
deposedBy
Indicates that an entity has been removed from a position of power or authority by another entity.
-
B.
canBeSuedFor
Indicates that one party is legally liable or potentially subject to legal action by another party for a specified cause or wrongdoing.
-
C.
canBeSuedAs
Indicates that one entity has legal standing or capacity to be the target of a lawsuit initiated by another entity.
-
D.
deposedInContextOf
chosen
Indicates that an entity was removed from power or office specifically within, or as a consequence of, a particular event, situation, or broader contextual circumstance.
-
E.
canCallAsWitness
Indicates that one party is permitted or eligible to summon another party to provide testimony as a witness in a proceeding.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f0951288190a809554f58be124f |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:23 p.m.