Triple
T28854776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orvietani |
E728703
|
entity |
| Predicate | associatedWithUrbanForm |
P67280
|
FINISHED |
| Object | medieval hill town |
—
|
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: medieval hill town | Statement: [Orvietani, associatedWithUrbanForm, medieval hill town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithUrbanForm Context triple: [Orvietani, associatedWithUrbanForm, medieval hill town]
-
A.
containsUrbanForm
Indicates that one entity spatially includes or encompasses an urban form or built-up area within its extent.
-
B.
isUrbanForm
chosen
Indicates that an entity represents or exhibits characteristics of an urban built environment or city-like spatial structure.
-
C.
formsUrbanAreaWith
Indicates that two or more settlements are geographically and functionally connected so that together they constitute a single continuous urban area.
-
D.
hasUrbanRelation
Indicates a relationship where one entity is connected to another through an urban context, such as city-based location, influence, or interaction.
-
E.
formsUrbanAxisWith
Indicates that two urban elements are aligned or arranged together to create a continuous, structured spatial or visual axis within the city.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a0204dafcc08190868a6f3eab162505 |
completed | May 11, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_6a0202dc60348190a140bb9da906f5b6 |
completed | May 11, 2026, 4:25 p.m. |
Created at: April 28, 2026, 6:45 a.m.