Triple
T23662853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ὑπερμνήστρα |
E584495
|
entity |
| Predicate | commandDisobeyed |
P60068
|
FINISHED |
| Object | order of Danaus to kill Lynceus |
—
|
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: order of Danaus to kill Lynceus | Statement: [Ὑπερμνήστρα, commandDisobeyed, order of Danaus to kill Lynceus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandDisobeyed Context triple: [Ὑπερμνήστρα, commandDisobeyed, order of Danaus to kill Lynceus]
-
A.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
B.
commandedOperationAgainst
Indicates that one entity issued authoritative orders to initiate or conduct a specific military or strategic operation directed against another entity.
-
C.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
D.
commandRefused
chosen
Indicates that an issued command was not accepted or carried out by the intended recipient.
-
E.
thenObeyedCommand
Indicates that one entity subsequently complied with or carried out a command issued by another entity.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4094c448190be12402422451e89 |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.