Triple
T36810417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surena |
E909571
|
entity |
| Predicate | consequenceOfVictory |
P27457
|
FINISHED |
| Object | major Roman losses in men and standards |
—
|
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: major Roman losses in men and standards | Statement: [Surena, consequenceOfVictory, major Roman losses in men and standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfVictory Context triple: [Surena, consequenceOfVictory, major Roman losses in men and standards]
-
A.
victoryIn
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
-
B.
typeOfVictory
Indicates the specific manner or category in which a victory was achieved.
-
C.
strategicEffectOfVictory
chosen
Indicates that a victory produces a broader strategic impact or consequence beyond the immediate outcome of the conflict or contest.
-
D.
conditionOfVictory
Indicates the specific circumstances or criteria under which a participant is considered to have won.
-
E.
afterConquest
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:13 p.m.