Triple
T2304068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romans |
E51795
|
entity |
| Predicate | citizenshipConcept |
P13310
|
FINISHED |
| Object | Roman citizenship |
—
|
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: Roman citizenship | Statement: [Romans, citizenshipConcept, Roman citizenship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citizenshipConcept Context triple: [Romans, citizenshipConcept, Roman citizenship]
-
A.
definedCitizenship
Indicates that a formal citizenship status has been legally established or specified for an entity.
-
B.
countryOfCitizenship
Indicates the country in which a person or entity holds legal citizenship.
-
C.
laterCitizenship
Indicates that an entity acquired citizenship in a country or polity at a later point in time, after some earlier status or affiliation.
-
D.
acquireCitizenshipBy
Indicates the process or means by which an entity obtains or is granted citizenship through a specific method, action, or legal basis.
-
E.
citizenshipLinkedTo
chosen
Indicates that there is an established connection between an entity and a specific citizenship status, such as holding, sharing, or being associated with that citizenship.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcbabf01081908db3b42bc7c60444 |
completed | March 7, 2026, 6:54 a.m. |
| PD | Predicate disambiguation | batch_69abc58ad33c8190b8d68af41b6f5e07 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.