Triple
T30462567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vologases V of Parthia |
E775050
|
entity |
| Predicate | territorialLossesToRome |
P59429
|
FINISHED |
| Object | parts of Mesopotamia |
—
|
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: parts of Mesopotamia | Statement: [Vologases V of Parthia, territorialLossesToRome, parts of Mesopotamia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: territorialLossesToRome Context triple: [Vologases V of Parthia, territorialLossesToRome, parts of Mesopotamia]
-
A.
causedTerritorialLossesTo
chosen
Indicates that one entity was responsible for another entity losing control over some portion of its territory.
-
B.
eraOfRomanConquest
Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
-
C.
CarthaginianLosses
Indicates the number or extent of losses suffered by the Carthaginians in a given conflict or event.
-
D.
ItalianLosses
Indicates that the relationship concerns losses (such as casualties, equipment, or territory) incurred by Italian forces or entities.
-
E.
conqueredInPartBy
Indicates that one entity has gained control over a portion, but not the entirety, of another entity through conquest.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 8:10 p.m.