Triple
T36237476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Dept. |
E891412
|
entity |
| Predicate | buildingBorough |
P300
|
FINISHED |
| Object | Manhattan |
—
|
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: Manhattan | Statement: [1st Dept., buildingBorough, Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingBorough Context triple: [1st Dept., buildingBorough, Manhattan]
-
A.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
-
B.
projectBorough
Indicates that a project is associated with, located in, or administered within a specific borough.
-
C.
hasBorough
chosen
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
D.
wasBoroughOf
Indicates that one place previously held the administrative or territorial status of a borough within another jurisdiction.
-
E.
cityCouncilBorough
Indicates that a city council has jurisdiction over, or is associated with, a specific borough within the city.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:09 p.m.