Triple
T8310113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arpinum |
E194569
|
entity |
| Predicate | grantedFullRomanCitizenship |
P81741
|
FINISHED |
| Object | 90 BC |
—
|
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: 90 BC | Statement: [Arpinum, grantedFullRomanCitizenship, 90 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedFullRomanCitizenship Context triple: [Arpinum, grantedFullRomanCitizenship, 90 BC]
-
A.
grantedToEmperor
Indicates that something (such as a right, title, privilege, or possession) has been formally given or conferred to an emperor.
-
B.
grantedCitizenshipBy
chosen
Indicates that one entity has officially conferred citizenship status upon another entity.
-
C.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
D.
grantsRecognitionTo
Indicates that one entity formally acknowledges, honors, or validates another entity’s achievements, status, or contributions.
-
E.
citizenshipRestored
Indicates that an individual's previously lost or revoked citizenship has been officially reinstated by the relevant authority.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f2d2c30819095075940479b75a7 |
completed | March 31, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.