Triple
T26928068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seward Square |
E678135
|
entity |
| Predicate | isInNeighborhoodType |
P162006
|
FINISHED |
| Object | residential neighborhood |
—
|
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: residential neighborhood | Statement: [Seward Square, isInNeighborhoodType, residential neighborhood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInNeighborhoodType Context triple: [Seward Square, isInNeighborhoodType, residential neighborhood]
-
A.
hasNeighborhoodRole
Indicates that an entity holds a specific role, function, or position within a neighborhood or local community context.
-
B.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
C.
hasNearbyPropertyType
Indicates that one entity has another entity of a specified property type located in close physical proximity to it.
-
D.
hasNeighbourhoodStatus
Indicates that an entity has a particular status, classification, or condition specifically in relation to a given neighbourhood.
-
E.
hasNeighborhoodAssociation
Indicates that an entity is associated with, or falls under the jurisdiction of, a particular neighborhood association.
- F. None of above. chosen
Provenance (4 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621c7d3e0819095b1f327637ae4f9 |
completed | May 2, 2026, 4:09 p.m. |
Created at: April 27, 2026, 6:10 a.m.