Triple
T883610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millbrook |
E19079
|
entity |
| Predicate | isResidentialAreaFor |
P9064
|
FINISHED |
| Object | New York City weekend residents |
—
|
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: New York City weekend residents | Statement: [Millbrook, isResidentialAreaFor, New York City weekend residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResidentialAreaFor Context triple: [Millbrook, isResidentialAreaFor, New York City weekend residents]
-
A.
hasResidentialArea
chosen
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
B.
isResidentialSuburbOf
Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
-
C.
isResidentialHubIn
Indicates that a location functions primarily as a residential center or hub within a specified larger area or region.
-
D.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
E.
isInBusinessDistrict
Indicates that an entity is located within a designated business or commercial district area.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4accda4148190aa628dab14d7f5de |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8eca748190b58e0f08b30fba43 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.