Triple
T35766155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Augustus and Rome |
E1034020
|
entity |
| Predicate | regionOfRomanEmpire |
P58441
|
FINISHED |
| Object | Galatia |
E64910
|
NE 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: Galatia | Statement: [Temple of Augustus and Rome, regionOfRomanEmpire, Galatia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfRomanEmpire Context triple: [Temple of Augustus and Rome, regionOfRomanEmpire, Galatia]
-
A.
countryDuringByzantinePeriod
Indicates that a modern or historical country existed within, or is contextually associated with, the geographic or political realm of the Byzantine Empire during the Byzantine period.
-
B.
preRomanRegion
Indicates that a region existed or was defined in the period before Roman rule or influence.
-
C.
regionDuringEmpire
chosen
Indicates that a region existed within or was governed by a particular empire during a specified historical period.
-
D.
countryDuringAntiquity
Indicates that an entity functioned as a country or political territory specifically during the historical period of antiquity.
-
E.
romanProvinceAfterConquest
Indicates that a territory became a Roman province following its military conquest by Rome.
- F. None of above.
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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffebbd9bac8190b3dca4b7252a2278 |
completed | May 10, 2026, 2:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38915a6bd081908d6638afde1a31f7 |
completed | June 22, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69ffe93120a08190a44bb64d052eda78 |
completed | May 10, 2026, 2:10 a.m. |
Created at: May 3, 2026, 4:06 p.m.