Triple
T5999608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arelate |
E133561
|
entity |
| Predicate | cameUnderRomanControl |
P22322
|
FINISHED |
| Object | 123 BC |
—
|
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: 123 BC | Statement: [Arelate, cameUnderRomanControl, 123 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameUnderRomanControl Context triple: [Arelate, cameUnderRomanControl, 123 BC]
-
A.
governedInAntiquityBy
Indicates that one entity exercised political rule or authority over another entity during ancient or classical historical periods.
-
B.
regionDuringEmpire
Indicates that a region existed within or was governed by a particular empire during a specified historical period.
-
C.
underRomanRule
chosen
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
D.
romanRuleEnded
Indicates that a period of Roman political or administrative control over a place or people has come to an end.
-
E.
romanIntegrationProcess
Indicates the process by which Roman authority, culture, and systems were incorporated into or imposed upon a territory, population, or institution.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04ee5e7bc8190aaa87605fa7b102e |
completed | March 22, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.