Triple
T9419634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York's 19th congressional district |
E227118
|
entity |
| Predicate | hasTypeOfCommunities |
P3292
|
FINISHED |
| Object | urban |
—
|
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: urban | Statement: [New York's 19th congressional district, hasTypeOfCommunities, urban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfCommunities Context triple: [New York's 19th congressional district, hasTypeOfCommunities, urban]
-
A.
hasCommunityType
chosen
Indicates that an entity is associated with or classified under a particular type or category of community.
-
B.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
C.
hasTargetCommunity
Indicates that something is specifically intended for, directed toward, or designed to serve a particular community or group.
-
D.
hasCommunityGroup
Indicates that an entity is associated with, or belongs to, a specific community group.
-
E.
hasGatedCommunities
Indicates that one entity possesses, contains, or includes one or more gated residential communities within its domain or boundaries.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd6c23c65081908d1009c26be66533 |
completed | April 1, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:48 p.m.