Triple
T13906166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marple Hall School |
E334355
|
entity |
| Predicate | hasUrbanRuralDescription |
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: [Marple Hall School, hasUrbanRuralDescription, urban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanRuralDescription Context triple: [Marple Hall School, hasUrbanRuralDescription, urban]
-
A.
isRuralOrUrban
chosen
Indicates whether an entity is classified as being in a rural area or an urban area.
-
B.
hasUrbanRuralGmina
Indicates that an entity is associated with a specific urban-rural gmina (a mixed urban and rural municipal administrative unit).
-
C.
hasRuralLocality
Indicates that an entity possesses, includes, or is associated with a rural locality (such as a village, hamlet, or countryside settlement) within its scope or jurisdiction.
-
D.
hasUrbanRuralMix
Indicates that something exhibits a combination or blend of both urban and rural characteristics or components.
-
E.
urbanRuralSplit
Indicates a division or distinction between urban and rural areas, conditions, or populations.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de25dc26cc8190a7909980b1d34933 |
completed | April 14, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:16 p.m.