Triple
T28219488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogontiacum |
E711411
|
entity |
| Predicate | hadUrbanFeatures |
P1495
|
FINISHED |
| Object | baths |
—
|
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: baths | Statement: [Mogontiacum, hadUrbanFeatures, baths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadUrbanFeatures Context triple: [Mogontiacum, hadUrbanFeatures, baths]
-
A.
hasUrbanFeature
chosen
Indicates that a place or area possesses a specific urban element or infrastructure feature (such as roads, parks, or buildings) as part of its built environment.
-
B.
hasUrbanFunction
Indicates that an entity serves a specific role or purpose within an urban context, such as providing services, infrastructure, or activities typical of a city environment.
-
C.
hasUrbanFabric
Indicates that one entity possesses, contains, or is characterized by a particular pattern or structure of built-up urban development.
-
D.
hasUrbanSectionsIn
Indicates that an entity includes or contains sections that are classified as urban within a specified area or region.
-
E.
hasUrbanAreaCharacter
Indicates that something possesses qualities, features, or conditions typical of an urban area.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6434f9f888190bd43fde92cd729fe |
completed | May 2, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 10:45 p.m.