Triple
T33838507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydatius of Aquae Flaviae |
E867298
|
entity |
| Predicate | AquaeFlaviaeLocatedIn |
P166890
|
FINISHED |
| Object | Gallaecia |
—
|
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: Gallaecia | Statement: [Hydatius of Aquae Flaviae, AquaeFlaviaeLocatedIn, Gallaecia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AquaeFlaviaeLocatedIn Context triple: [Hydatius of Aquae Flaviae, AquaeFlaviaeLocatedIn, Gallaecia]
-
A.
romanTownLocatedIn
chosen
Indicates that a Roman town is geographically situated within a specified larger area, such as a region, province, or territory.
-
B.
romanFortAssociatedWith
Indicates that there is a relationship of historical, functional, or spatial connection between a Roman fort and another entity.
-
C.
wasRomanTown
Indicates that the subject entity functioned as a town or urban settlement during the period of the Roman Empire.
-
D.
mainRomanSanctuary
Indicates that one entity serves as the primary Roman religious sanctuary or temple associated with another entity.
-
E.
wasRomanSettlementName
Indicates that the subject was the name used for a settlement during the Roman 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7004d97408190a3b09fa2bda3d42e |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.