Triple
T37406839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glanum |
E929154
|
entity |
| Predicate | romanizationPeriod |
P188038
|
FINISHED |
| Object | 1st century BCE |
—
|
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: 1st century BCE | Statement: [Glanum, romanizationPeriod, 1st century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanizationPeriod Context triple: [Glanum, romanizationPeriod, 1st century BCE]
-
A.
romanizationBegan
Indicates that the process of converting text from one writing system into its representation using the Roman (Latin) alphabet was initiated.
-
B.
romanizationOccurred
Indicates that a process of converting text from one writing system into the Roman (Latin) alphabet has taken place.
-
C.
romanizationStandardReplacedBy
Indicates that one system or convention for romanization has been superseded and replaced by another romanization standard.
-
D.
romanizationType
Indicates the specific system or method used to convert text from one writing system into its Roman (Latin) alphabet representation.
-
E.
romanizationProcess
Indicates the process of converting text from a non-Latin writing system into a representation using the Latin alphabet.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.