Triple
T21220039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queens Community District 2 |
E522941
|
entity |
| Predicate | containsNeighborhood |
P4813
|
FINISHED |
| Object | Blissville |
—
|
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: Blissville | Statement: [Queens Community District 2, containsNeighborhood, Blissville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Blissville Context triple: [Queens Community District 2, containsNeighborhood, Blissville]
-
A.
Blissville
chosen
Blissville is a small, historically industrial neighborhood in western Queens, New York City, known for its proximity to major rail yards and cemeteries.
-
B.
Snowville
Snowville is a small rural settlement located within the township of Tehkummah in Ontario, Canada.
-
C.
Richville
Richville is a small unincorporated community located in Morgan County in the U.S. state of Missouri.
-
D.
Richville
Richville was the original settlement that later developed into the city of Wahpeton in southeastern North Dakota.
-
E.
Maxville
Maxville is a small unincorporated community located in the state of Missouri in the United States.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b511ed84819099b449b4a111085c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73477957081908ab9ad11f51d15fd |
completed | April 21, 2026, 8:25 a.m. |
Created at: April 16, 2026, 3:43 p.m.