Triple
T23010398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viromandui |
E572888
|
entity |
| Predicate | romanPeriodStatus |
P63218
|
FINISHED |
| Object | civitas of Gallia Belgica |
—
|
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: civitas of Gallia Belgica | Statement: [Viromandui, romanPeriodStatus, civitas of Gallia Belgica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanPeriodStatus Context triple: [Viromandui, romanPeriodStatus, civitas of Gallia Belgica]
-
A.
romanStatus
chosen
Indicates the status or condition of an entity within a Roman-specific context, such as its legal, social, or civic standing in Roman society.
-
B.
preRomanStatus
Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
-
C.
statusInLateAntiquity
Indicates the social, political, or cultural standing that an entity held during the historical period of Late Antiquity.
-
D.
statusAfterRomanConquest
Indicates the condition or standing of an entity following its conquest by the Roman state or Roman forces.
-
E.
statusInLateEmpire
Indicates the social, legal, or political standing an entity held during the later period of an empire.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18359f5548190b15a139eb09e30a0 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.