Triple
T8156531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steyning Grammar School |
E190463
|
entity |
| Predicate | servesRuralArea |
P80865
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Steyning Grammar School, servesRuralArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRuralArea Context triple: [Steyning Grammar School, servesRuralArea, true]
-
A.
hasRuralServiceTown
Indicates that a rural area or region is associated with, and typically receives services from, a specific town that functions as its service center.
-
B.
ruralCoverage
Indicates the extent to which a service, infrastructure, or resource is available or provided in rural areas.
-
C.
isInRuralAreaOf
Indicates that one entity is located within the rural area or countryside region associated with another entity.
-
D.
hasRuralArea
Indicates that an entity includes, is associated with, or contains a countryside or sparsely populated geographic area.
-
E.
isRuralServiceTown
Indicates that a town functions primarily as a service and support center for surrounding rural or agricultural areas.
- F. None of above. chosen
Provenance (4 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44d8a37481909397b5cc321b94be |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb39ba412881908a053e88f29a9588 |
completed | March 31, 2026, 3:04 a.m. |
Created at: March 30, 2026, 5:37 p.m.