Triple
T30162800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tungri |
E766712
|
entity |
| Predicate | romanCitizenshipGrantedTo |
P81741
|
FINISHED |
| Object | auxiliary veterans |
—
|
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: auxiliary veterans | Statement: [Tungri, romanCitizenshipGrantedTo, auxiliary veterans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanCitizenshipGrantedTo Context triple: [Tungri, romanCitizenshipGrantedTo, auxiliary veterans]
-
A.
grantedToEmperor
Indicates that something (such as a right, title, privilege, or possession) has been formally given or conferred to an emperor.
-
B.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
C.
grantedCitizenshipBy
chosen
Indicates that one entity has officially conferred citizenship status upon another entity.
-
D.
allyOfRome
Indicates a relationship where one entity is politically or militarily aligned with, and offers support or cooperation to, Rome.
-
E.
becameRomanColony
Indicates that a place or community transitioned into the formal status of a Roman colony under Roman 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 29, 2026, 7:22 p.m.