Triple
T8916150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mixed constitution (Sparta) |
E212300
|
entity |
| Predicate | hasCheckOnKings |
P86364
|
FINISHED |
| Object | ephors |
—
|
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: ephors | Statement: [mixed constitution (Sparta), hasCheckOnKings, ephors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckOnKings Context triple: [mixed constitution (Sparta), hasCheckOnKings, ephors]
-
A.
hasKing
Indicates that an entity possesses or is ruled by a king.
-
B.
kingIsInviolable
Indicates that the king is protected from harm, violation, or infringement, often implying legal or moral immunity from certain actions.
-
C.
hasKingAsSubject
Indicates that the subject entity in the relationship is a king.
-
D.
evaluatesKingsBy
Indicates a relationship where an agent assesses or judges kings according to a specified criterion, standard, or method.
-
E.
opponentKing
Indicates that one entity is the king belonging to the opposing or rival side of the other 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc660f6a088190b0af829ea809d8ad |
completed | April 1, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc600a59708190ae426044bbcd7929 |
completed | April 1, 2026, midnight |
Created at: March 30, 2026, 6:56 p.m.