Triple
T19277349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Sicily |
E482090
|
entity |
| Predicate | significanceToRome |
P135413
|
FINISHED |
| Object | first overseas province |
—
|
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: first overseas province | Statement: [Roman Sicily, significanceToRome, first overseas province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significanceToRome Context triple: [Roman Sicily, significanceToRome, first overseas province]
-
A.
allyOfRome
Indicates a relationship where one entity is politically or militarily aligned with, and offers support or cooperation to, Rome.
-
B.
aimOfRome
Indicates that something is the goal, purpose, or intended objective of Rome.
-
C.
hillOfRome
Indicates that one entity is a hill that is located in or associated with the city of Rome.
-
D.
eraOfSignificance
Indicates the historical period or timeframe during which an entity was particularly important, influential, or noteworthy.
-
E.
sideRoman
Indicates that one entity is located on the Roman (Latin-script) side or version of another entity, typically in contrast to a non-Roman or alternative script side.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbd5f34819086535f28fd880411 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:30 p.m.