Triple
T3045725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulpia Noviomagus Batavorum |
E83441
|
entity |
| Predicate | hasCivicStatus |
P43827
|
FINISHED |
| Object | municipium |
—
|
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: municipium | Statement: [Ulpia Noviomagus Batavorum, hasCivicStatus, municipium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCivicStatus Context triple: [Ulpia Noviomagus Batavorum, hasCivicStatus, municipium]
-
A.
hasCivicFunction
Indicates that an entity performs, is responsible for, or is associated with an official public or civic role, duty, or service.
-
B.
electoralStatus
Indicates the current state or condition of an entity in relation to an election process (e.g., running, elected, defeated, or not a candidate).
-
C.
politicalStatusContext
Indicates the situational or contextual conditions under which a particular political status holds or is evaluated.
-
D.
hasCivicOrganization
Indicates that an entity is associated with, supported by, or contains a civic organization, such as a community, volunteer, or public-interest group.
-
E.
hasTownStatus
chosen
Indicates that an entity possesses the legal or administrative status of being recognized as a town.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bab541c8190a17aca26b3dcfae7 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.