Triple
T30168025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spartan kings |
E766846
|
entity |
| Predicate | couldBeTriedBy |
P139167
|
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: [Spartan kings, couldBeTriedBy, ephors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: couldBeTriedBy Context triple: [Spartan kings, couldBeTriedBy, ephors]
-
A.
triedBy
Indicates that an entity has made an attempt to perform an action on, or in relation to, another entity.
-
B.
canTry
Indicates that an entity has the possibility or permission to attempt performing a particular action or achieving a certain outcome.
-
C.
wasTriedBy
Indicates that a legal case or charge involving an entity was examined and judged in a trial conducted by another entity (such as a court or judge).
-
D.
mayBeAdaptedTo
Indicates that something has the potential or suitability to be modified or adjusted for use in a different context, condition, or purpose.
-
E.
canUndergo
chosen
Indicates that one entity is capable of experiencing, being subjected to, or participating in a specified process, action, or transformation.
- 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_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:23 p.m.