Triple
T14269422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ager Gallicus |
E353738
|
entity |
| Predicate | languagePreRoman |
P88155
|
FINISHED |
| Object | Gaulish |
—
|
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: Gaulish | Statement: [Ager Gallicus, languagePreRoman, Gaulish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languagePreRoman Context triple: [Ager Gallicus, languagePreRoman, Gaulish]
-
A.
preRomanLanguage
chosen
Indicates that a language existed or was used in a region before the arrival or dominance of Roman rule or the Latin language.
-
B.
ancientLanguages
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
-
C.
preRomanName
Indicates the name by which an entity (such as a place or people) was known before the Roman period or prior to receiving a Roman-era name.
-
D.
preRomanContext
Indicates that something exists, occurs, or is situated in a historical or cultural context prior to the Roman period.
-
E.
religionInPreRomanPeriod
Indicates the religion or belief system practiced in a place or by a group during the period before Roman rule.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de657fe6708190b41de48c43cff647 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.