Triple
T9445250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Placentia |
E227746
|
entity |
| Predicate | citizenStatus |
P50609
|
FINISHED |
| Object | Roman citizens and Latin colonists |
—
|
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 citizens and Latin colonists | Statement: [Placentia, citizenStatus, Roman citizens and Latin colonists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citizenStatus Context triple: [Placentia, citizenStatus, Roman citizens and Latin colonists]
-
A.
citizenshipType
chosen
Indicates the specific legal category or status of an individual's citizenship in relation to a state or country.
-
B.
definedCitizenship
Indicates that a formal citizenship status has been legally established or specified for an entity.
-
C.
isPoliticalStatus
Indicates that a relationship specifies the political condition, classification, or standing associated with an entity.
-
D.
civicStatus
Indicates the legal or social standing of an individual within a civic or societal framework, such as marital or citizenship status.
-
E.
politicalStatusContext
Indicates the situational or contextual conditions under which a particular political status holds or is evaluated.
- 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f33deb88190bc74968575963ac4 |
completed | April 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:51 p.m.