Triple
T14513239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars Ultor |
E340449
|
entity |
| Predicate | vowReason |
P59825
|
FINISHED |
| Object | avenge Julius Caesar |
—
|
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: avenge Julius Caesar | Statement: [Mars Ultor, vowReason, avenge Julius Caesar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vowReason Context triple: [Mars Ultor, vowReason, avenge Julius Caesar]
-
A.
causeOfVow
chosen
Indicates that one event, condition, or entity is the reason or motivating factor behind another entity making a vow.
-
B.
reasonForVeto
Indicates the specific justification or grounds given for issuing a veto.
-
C.
vowStatus
Indicates the current state or condition of a commitment or promise made between entities, such as whether it is active, fulfilled, or broken.
-
D.
vowResult
Indicates that a vow or solemn promise leads to, results in, or is fulfilled by a particular outcome or state.
-
E.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a6c6054819086b4c0ce1d83fdc5 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.