Triple
T31048685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman province of Picenum |
E791196
|
entity |
| Predicate | grantedRomanCitizenshipTo |
P81741
|
FINISHED |
| Object | local communities |
—
|
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: local communities | Statement: [Roman province of Picenum, grantedRomanCitizenshipTo, local communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedRomanCitizenshipTo Context triple: [Roman province of Picenum, grantedRomanCitizenshipTo, local communities]
-
A.
soughtRomanCitizenship
Indicates that an entity actively attempted to obtain or be granted Roman citizenship.
-
B.
grantedToEmperor
Indicates that something (such as a right, title, privilege, or possession) has been formally given or conferred to an emperor.
-
C.
grantedCitizenshipBy
chosen
Indicates that one entity has officially conferred citizenship status upon another entity.
-
D.
acclaimedAugustusBy
Indicates that one entity formally praised, honored, or recognized Augustus.
-
E.
allyOfRome
Indicates a relationship where one entity is politically or militarily aligned with, and offers support or cooperation to, Rome.
- 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_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 29, 2026, 9 p.m.