Triple
T3045754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulpia Noviomagus Batavorum |
E83441
|
entity |
| Predicate | hasTypeSiteFor |
P44791
|
FINISHED |
| Object | Batavian Roman urbanism |
—
|
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: Batavian Roman urbanism | Statement: [Ulpia Noviomagus Batavorum, hasTypeSiteFor, Batavian Roman urbanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeSiteFor Context triple: [Ulpia Noviomagus Batavorum, hasTypeSiteFor, Batavian Roman urbanism]
-
A.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
coversTypeOfSite
Indicates that one entity provides coverage or applies to a particular category or type of site.
-
D.
hasTypeSystem
Indicates that an entity employs, is governed by, or is associated with a particular type system (a defined set of rules for classifying and constraining types).
-
E.
isSiteSpecific
Indicates that something is designed, intended, or valid only for a particular location, context, or site and does not generally apply elsewhere.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bab541c8190a17aca26b3dcfae7 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:01 p.m.