Triple
T17393123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pound Ridge Volunteer Fire Department |
E422877
|
entity |
| Predicate | usesStaffCategory |
P127311
|
FINISHED |
| Object | volunteer firefighters |
—
|
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: volunteer firefighters | Statement: [Pound Ridge Volunteer Fire Department, usesStaffCategory, volunteer firefighters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStaffCategory Context triple: [Pound Ridge Volunteer Fire Department, usesStaffCategory, volunteer firefighters]
-
A.
usesStaffCode
Indicates that one entity performs an action or operates by referencing or applying a specific staff code associated with another entity.
-
B.
hadStaffRole
Indicates that an entity served in a specific staff role or position for another entity during some period.
-
C.
usesCategorySystem
Indicates that one entity organizes or classifies things according to a particular category system defined by another entity.
-
D.
eligibilityCategory
Indicates the classification or type of eligibility that applies to an entity within a given context.
-
E.
hasAdultStaffRole
Indicates that an entity holds a staff position or role designated specifically for adults.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43abb23888190812aad44288c90fd |
completed | April 19, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:45 a.m.