Triple
T10251219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raeti |
E240344
|
entity |
| Predicate | laterRomanStatus |
P58764
|
FINISHED |
| Object | provincial population of Raetia |
—
|
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: provincial population of Raetia | Statement: [Raeti, laterRomanStatus, provincial population of Raetia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRomanStatus Context triple: [Raeti, laterRomanStatus, provincial population of Raetia]
-
A.
romanStatus
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.
statusInLateAntiquity
chosen
Indicates the social, political, or cultural standing that an entity held during the historical period of Late Antiquity.
-
C.
preRomanStatus
Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
-
D.
postRomanSuccessor
Indicates that one entity serves as the political or cultural successor to another entity following the end of Roman rule.
-
E.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:29 a.m.