Triple
T36581908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond County |
E902418
|
entity |
| Predicate | boroughStatusIncorporatedIntoNewYorkCity |
P2381
|
FINISHED |
| Object | 1898 |
—
|
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: 1898 | Statement: [Richmond County, boroughStatusIncorporatedIntoNewYorkCity, 1898]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boroughStatusIncorporatedIntoNewYorkCity Context triple: [Richmond County, boroughStatusIncorporatedIntoNewYorkCity, 1898]
-
A.
incorporatedAsBorough
chosen
Indicates that an entity was formally established and granted legal status as a borough.
-
B.
abolishedAsBorough
Indicates that an entity ceased to exist or function in its status as a borough, typically due to formal abolition or administrative reorganization.
-
C.
boroughOfNewYorkCity
Indicates that one entity is a borough that is officially part of New York City.
-
D.
locatedInFormerBorough
Indicates that an entity is or was situated within the geographic area of a borough that no longer exists as an administrative unit.
-
E.
wasBoroughOf
Indicates that one place previously held the administrative or territorial status of a borough within another jurisdiction.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.