Triple
T29668228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 47th Precinct station house |
E750592
|
entity |
| Predicate | operationalHeadquartersOf |
P52556
|
FINISHED |
| Object | 47th Precinct |
—
|
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: 47th Precinct | Statement: [47th Precinct station house, operationalHeadquartersOf, 47th Precinct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalHeadquartersOf Context triple: [47th Precinct station house, operationalHeadquartersOf, 47th Precinct]
-
A.
headquartersAt
Indicates that an organization’s main administrative center or primary office is located at a specified place.
-
B.
headquartersFor
Indicates that a location serves as the main administrative center or base of operations for an organization or entity.
-
C.
headquartersOfOffice
Indicates that a particular location serves as the main headquarters for a specified office or organizational unit.
-
D.
headquartersStation
chosen
Indicates that a particular station serves as the main headquarters location for an organization or entity.
-
E.
headquartersFunction
Indicates that an entity serves as the main administrative or central operating location (headquarters) for another 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff1e3e13c08190bb8990c44716b746 |
completed | May 9, 2026, 11:45 a.m. |
| PD | Predicate disambiguation | batch_69ff1dfcaf2c8190aaf2b428d57b7782 |
completed | May 9, 2026, 11:43 a.m. |
Created at: April 28, 2026, 7:02 p.m.