Triple
T22114630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottone |
E546505
|
entity |
| Predicate | orderedTo |
P111331
|
FINISHED |
| Object | assassinate Poppea |
—
|
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: assassinate Poppea | Statement: [Ottone, orderedTo, assassinate Poppea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderedTo Context triple: [Ottone, orderedTo, assassinate Poppea]
-
A.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
B.
orden
chosen
Indicates that one entity issues, gives, or establishes an order, command, or directive concerning another entity or situation.
-
C.
orderedToward
Indicates that one entity is arranged, directed, or positioned in the direction of another entity or reference point.
-
D.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
E.
orderedToBear
Indicates that one entity has issued a command or directive requiring another entity to carry, support, or endure something.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1294c5f908190bdb1cce3cbf86d85 |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.