Triple
T31048684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman province of Picenum |
E791196
|
entity |
| Predicate | romanConquestCompletedBy |
P126247
|
FINISHED |
| Object | 3rd century BCE |
—
|
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: 3rd century BCE | Statement: [Roman province of Picenum, romanConquestCompletedBy, 3rd century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanConquestCompletedBy Context triple: [Roman province of Picenum, romanConquestCompletedBy, 3rd century BCE]
-
A.
eraOfRomanConquest
Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
-
B.
RomanVictory
Indicates that the Romans achieved a successful military outcome over their opponents.
-
C.
statusAfterRomanConquest
Indicates the condition or standing of an entity following its conquest by the Roman state or Roman forces.
-
D.
approximateRomanConquestCentury
chosen
Indicates the approximate century in which the Romans conquered or gained control over a given entity.
-
E.
romanRuleEnded
Indicates that a period of Roman political or administrative control over a place or people has come to an end.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 9 p.m.