Triple
T19981878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caius Marcius Coriolanus |
E493834
|
entity |
| Predicate | changesDecisionAbout |
P120620
|
FINISHED |
| Object | sacking Rome |
—
|
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: sacking Rome | Statement: [Caius Marcius Coriolanus, changesDecisionAbout, sacking Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changesDecisionAbout Context triple: [Caius Marcius Coriolanus, changesDecisionAbout, sacking Rome]
-
A.
changesMindAfter
chosen
Indicates that one entity revises or reverses a previously held decision, opinion, or intention after another entity’s action, statement, or influence.
-
B.
decisionsAre
Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
-
C.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
D.
decisiveFor
Indicates that one entity plays a determining or conclusive role in bringing about a particular outcome, decision, or state of another entity.
-
E.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d13a8a88190bf5f4f697793f4c9 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:28 p.m.