Triple
T23649775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustodunum – Autun |
E584135
|
entity |
| Predicate | roleInRomanPeriod |
P153034
|
FINISHED |
| Object | major city of Gaul |
—
|
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: major city of Gaul | Statement: [Augustodunum – Autun, roleInRomanPeriod, major city of Gaul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRomanPeriod Context triple: [Augustodunum – Autun, roleInRomanPeriod, major city of Gaul]
-
A.
roleInRome
Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
-
B.
roleInRaetia
Indicates that an entity held a specific role, position, or function within the Roman province of Raetia.
-
C.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
D.
underRomanEmperor
Indicates that one entity existed, occurred, or was governed during the reign of the specified Roman emperor.
-
E.
religionInRomanPeriod
Indicates that an entity’s religious affiliation, practice, or status is specified as it existed during the Roman period.
- F. None of above. chosen
Provenance (4 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2885b408190a43dfed93309a4d6 |
completed | April 29, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:49 p.m.