Triple
T34638563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hedwig Village |
E889494
|
entity |
| Predicate | hasFireServiceFrom |
P62810
|
FINISHED |
| Object | Village Fire Department |
—
|
NE NERFINISHED |
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: Village Fire Department | Statement: [Hedwig Village, hasFireServiceFrom, Village Fire Department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFireServiceFrom Context triple: [Hedwig Village, hasFireServiceFrom, Village Fire Department]
-
A.
hasFireServicesFrom
chosen
Indicates that one entity receives fire protection or firefighting services from another entity.
-
B.
hasFireRescueService
Indicates that an entity is served by, or responsible for providing, a fire and rescue service.
-
C.
hasFireStation
Indicates that a location or area contains or is served by a fire station.
-
D.
hasFireAndRescueServiceCategory
Indicates the specific fire and rescue service classification or category assigned to an entity, such as a building, facility, or site.
-
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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 1, 2026, 2:04 a.m.