Triple
T15456069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mytilenean Debate |
E371771
|
entity |
| Predicate | CleonArgues |
P2397
|
FINISHED |
| Object | terror as instrument of empire |
—
|
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: terror as instrument of empire | Statement: [Mytilenean Debate, CleonArgues, terror as instrument of empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CleonArgues Context triple: [Mytilenean Debate, CleonArgues, terror as instrument of empire]
-
A.
arguesThat
chosen
Indicates that one entity presents reasons or justification in support of a specific claim, position, or proposition held about another entity or topic.
-
B.
canDebate
Indicates that one entity has the ability or permission to engage in a debate or argumentative discussion with another entity.
-
C.
argumentPositionOfCrito
Indicates that a specific argument occurs at a particular position within the dialogue or text of Crito.
-
D.
rearguedWith
Indicates that one party presented arguments again or renewed a previous debate or legal argument with another party.
-
E.
chargeInTrialOfSocrates
Indicates that an entity is a specific legal accusation formally brought against Socrates in his trial.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f146a2c8190882741af3ec15268 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:31 a.m.