Triple
T19726174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGPN |
E473732
|
entity |
| Predicate | hasRescueAndFireFightingService |
P127488
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [EGPN, hasRescueAndFireFightingService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRescueAndFireFightingService Context triple: [EGPN, hasRescueAndFireFightingService, yes]
-
A.
hasFireRescueService
chosen
Indicates that an entity is served by, or responsible for providing, a fire and rescue service.
-
B.
hasFireAndRescueServiceCategory
Indicates the specific fire and rescue service classification or category assigned to an entity, such as a building, facility, or site.
-
C.
hasFireServicesFrom
Indicates that one entity receives fire protection or firefighting services from another entity.
-
D.
hasRuralFireServiceBrigade
Indicates that a specified area or jurisdiction is served by a particular rural fire service brigade.
-
E.
hasFireServiceCollege
Indicates that an entity is associated with, or has jurisdiction over, a specific fire service training or educational college.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649f7bedc81908f784832c0fc10a1 |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:46 p.m.