Triple
T25313342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lingones |
E634664
|
entity |
| Predicate | capitalInRomanPeriod |
P134108
|
FINISHED |
| Object | Lingonae |
—
|
NE NERFINISHED |
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: Lingonae | Statement: [Lingones, capitalInRomanPeriod, Lingonae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalInRomanPeriod Context triple: [Lingones, capitalInRomanPeriod, Lingonae]
-
A.
capitalCityDuringEra
chosen
Indicates that a particular city served as the capital of an entity (such as a country or region) during a specified historical era or time period.
-
B.
romanProvinceCapital
Indicates that one place served as the administrative capital of a specified Roman province.
-
C.
romanCivitasName
Indicates that an entity bears the official Roman civitas (city or community) name associated with it.
-
D.
preRomanCenterOf
Indicates that a place served as the primary political, cultural, or administrative center of a region or community before the establishment of Roman control or influence.
-
E.
cityDuringImperialPeriod
Indicates that a location functioned as a city during a specified imperial or empire-dominated historical period.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 1:27 p.m.