Triple
T11212175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venta Belgarum |
E265334
|
entity |
| Predicate | wasUrbanCentreFor |
P54981
|
FINISHED |
| Object | surrounding rural 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 rural territory | Statement: [Venta Belgarum, wasUrbanCentreFor, surrounding rural territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasUrbanCentreFor Context triple: [Venta Belgarum, wasUrbanCentreFor, surrounding rural 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.
hasCityCentreLocation
Indicates that something is located in, or directly associated with, the central area of a city.
-
D.
isUrbanHubFor
Indicates that a location functions as a central urban focal point or primary service center for another area or population.
-
E.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d6f5d4819086dcb776a0d469e8 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.