Triple
T9734798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iuvavum |
E236029
|
entity |
| Predicate | wasUrbanCenterFor |
P54981
|
FINISHED |
| Object | surrounding Norican territory |
—
|
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: surrounding Norican territory | Statement: [Iuvavum, wasUrbanCenterFor, surrounding Norican territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasUrbanCenterFor Context triple: [Iuvavum, wasUrbanCenterFor, surrounding Norican territory]
-
A.
isUrbanCentreFor
chosen
Indicates that one place functions as the primary urban hub or central city serving another area or population.
-
B.
isUrbanCenter
Indicates that a place functions as a primary, densely developed hub of population, services, and activities within a region.
-
C.
isUrbanNeighborhood
Indicates that a given area functions as a neighborhood located within an urban or city environment.
-
D.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
-
E.
wasMajorCenterDuring
Indicates that a place served as a primary or highly significant hub of activity, influence, or importance during a specified time 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eebcec08190a9d4606fd26f2e19 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.