Triple
T9256503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Saguntum |
E222455
|
entity |
| Predicate | consideredByRomeAs |
P87817
|
FINISHED |
| Object | violation of the Ebro Treaty |
—
|
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: violation of the Ebro Treaty | Statement: [Siege of Saguntum, consideredByRomeAs, violation of the Ebro Treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredByRomeAs Context triple: [Siege of Saguntum, consideredByRomeAs, violation of the Ebro Treaty]
-
A.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
B.
romanStatus
Indicates the status or condition of an entity within a Roman-specific context, such as its legal, social, or civic standing in Roman society.
-
C.
viewedRomanRuleAs
Indicates that one entity regarded or interpreted Roman rule in a particular way or from a particular perspective.
-
D.
unionWithRomeConcludedAt
Indicates that the formal union with Rome was concluded or established at a specific place or time.
-
E.
reunionWithRomeProclaimedBy
Indicates that a reunion with Rome was formally announced or declared by a specific agent or authority.
- F. None of above. chosen
Provenance (4 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b4e2048190af0d65b904677c36 |
completed | April 1, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:32 p.m.