Triple
T10251126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augusta Vindelicorum |
E240342
|
entity |
| Predicate | roleInProvince |
P12921
|
FINISHED |
| Object | capital 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: capital of Raetia | Statement: [Augusta Vindelicorum, roleInProvince, capital of Raetia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInProvince Context triple: [Augusta Vindelicorum, roleInProvince, capital of Raetia]
-
A.
stationedInProvince
Indicates that an entity is assigned or based in a particular province as its location or area of operation.
-
B.
isInProvince
Indicates that one entity (typically a place or city) is located within the administrative boundaries of a specified province.
-
C.
provinceOf
Indicates that one administrative region functions as a province belonging to or governed by a larger territorial or political entity.
-
D.
hasRegionalRole
chosen
Indicates that an entity holds a specific role, function, or responsibility within a defined geographic region.
-
E.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
- 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:28 a.m.