Triple
T28793776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confluentes |
E727029
|
entity |
| Predicate | nearRomanFort |
P165592
|
FINISHED |
| Object | Castellum apud Confluentes |
—
|
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: Castellum apud Confluentes | Statement: [Confluentes, nearRomanFort, Castellum apud Confluentes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearRomanFort Context triple: [Confluentes, nearRomanFort, Castellum apud Confluentes]
-
A.
wasRomanFort
Indicates that the subject functioned as a Roman military fort at some point in time.
-
B.
nearbyRomanTown
Indicates that one location is geographically close to a town that existed during the Roman period.
-
C.
wasRomanSettlementName
Indicates that the subject was the name used for a settlement during the Roman period.
-
D.
wasRomanTown
Indicates that the subject entity functioned as a town or urban settlement during the period of the Roman Empire.
-
E.
mainRomanSanctuary
Indicates that one entity serves as the primary Roman religious sanctuary or temple associated with another entity.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:24 a.m.