Triple
T13731827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Yorkshire Fire and Rescue Service |
E329820
|
entity |
| Predicate | hasNumberOfFireStations |
P1301
|
FINISHED |
| Object | approximately 38 |
—
|
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: approximately 38 | Statement: [North Yorkshire Fire and Rescue Service, hasNumberOfFireStations, approximately 38]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfFireStations Context triple: [North Yorkshire Fire and Rescue Service, hasNumberOfFireStations, approximately 38]
-
A.
hasFireStation
Indicates that a location or area contains or is served by a fire station.
-
B.
hasFireServicesFrom
Indicates that one entity receives fire protection or firefighting services from another entity.
-
C.
hasPoliceStationsIn
Indicates that one entity possesses, manages, or contains one or more police stations located within the area or jurisdiction of another entity.
-
D.
numberOfFirefightersInvolved
Indicates the total count of firefighters who participated in or were involved in a specific event, incident, or operation.
-
E.
numberOfStations
chosen
Indicates the total count of stations associated with or contained by a given entity.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de01f92b588190be97ec4564dddd59 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.