Triple
T4285888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clusium |
E97266
|
entity |
| Predicate | romanAdministrativeStatus |
P36003
|
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: [Clusium, romanAdministrativeStatus, municipium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanAdministrativeStatus Context triple: [Clusium, romanAdministrativeStatus, municipium]
-
A.
administrativeStatusUnderRome
chosen
Indicates the type or level of administrative control or governance an entity was subject to within the Roman political system.
-
B.
formerAdministrativeStatus
Indicates that an entity previously held, but no longer holds, a particular administrative status or role.
-
C.
administrativeStatusCurrent
Indicates the current administrative status or condition of an entity within a governing or managing system.
-
D.
governingStatus
Indicates the political or administrative condition under which an entity is currently governed or exercising governing authority.
-
E.
regionStatus
Indicates the current condition, classification, or operational state assigned to a specific geographic or administrative region.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3505bff588190919a4ef547f607c2 |
completed | March 12, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.