Triple
T32231447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civitas Tungrorum |
E823350
|
entity |
| Predicate | romanRoadNetworkNode |
P179533
|
FINISHED |
| Object | Tongeren |
—
|
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: Tongeren | Statement: [Civitas Tungrorum, romanRoadNetworkNode, Tongeren]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanRoadNetworkNode Context triple: [Civitas Tungrorum, romanRoadNetworkNode, Tongeren]
-
A.
romanRoad
Indicates that one location is connected to another by a road constructed or used during the Roman period.
-
B.
romanFortAssociatedWith
Indicates that there is a relationship of historical, functional, or spatial connection between a Roman fort and another entity.
-
C.
transportRouteInAntiquity
Indicates that there existed a transportation route between entities during ancient or classical historical periods.
-
D.
mainRomanSanctuary
Indicates that one entity serves as the primary Roman religious sanctuary or temple associated with another entity.
-
E.
wasRomanTown
Indicates that the subject entity functioned as a town or urban settlement during the period of the Roman Empire.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 12:39 a.m.