Triple
T18117141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Priory School, Hitchin |
E433633
|
entity |
| Predicate | hasUrbanRuralClassification |
P60791
|
FINISHED |
| Object | urban |
—
|
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: urban | Statement: [The Priory School, Hitchin, hasUrbanRuralClassification, urban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanRuralClassification Context triple: [The Priory School, Hitchin, hasUrbanRuralClassification, urban]
-
A.
hasUrbanClassification
Indicates that an entity is assigned a specific urban status or category within a defined classification system.
-
B.
isRuralOrUrban
chosen
Indicates whether an entity is classified as being in a rural area or an urban area.
-
C.
hasUrbanRuralGmina
Indicates that an entity is associated with a specific urban-rural gmina (a mixed urban and rural municipal administrative unit).
-
D.
isUrbanAreaOfType
Indicates that a given area is classified as belonging to a specific type or category of urban area (e.g., city, town, suburb).
-
E.
isRural
Indicates that something is located in, characteristic of, or associated with a countryside or non-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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd67a2481909d27a4a49b095f8c |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.