Triple
T36151882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hub of the Pascack Valley |
E1045606
|
entity |
| Predicate | appliedToMunicipality |
P21214
|
FINISHED |
| Object | Westwood |
—
|
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: Westwood | Statement: [The Hub of the Pascack Valley, appliedToMunicipality, Westwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToMunicipality Context triple: [The Hub of the Pascack Valley, appliedToMunicipality, Westwood]
-
A.
affectsMunicipality
Indicates that one entity has an impact on, influences, or brings about changes in a specific municipality.
-
B.
isInMunicipality
chosen
Indicates that one entity (typically a place or address) is located within the administrative boundaries of a specific municipality.
-
C.
appliedInDistrict
Indicates that an application or action was submitted or carried out within a specific administrative district.
-
D.
isPartOfMunicipalityType
Indicates that one administrative unit or area belongs to, or is classified under, a specific type or category of municipality.
-
E.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: May 3, 2026, 4:08 p.m.