Triple
T29811144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newport residential towers |
E756965
|
entity |
| Predicate | targetResidentType |
P189337
|
FINISHED |
| Object | commuters to Manhattan |
—
|
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: commuters to Manhattan | Statement: [Newport residential towers, targetResidentType, commuters to Manhattan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetResidentType Context triple: [Newport residential towers, targetResidentType, commuters to Manhattan]
-
A.
hasTypicalResident
chosen
Indicates that an entity characteristically or commonly has a particular type of resident associated with it.
-
B.
residenceType
Indicates the kind or category of dwelling or living arrangement associated with an entity.
-
C.
usedForResidentsOf
Indicates that something is intended to be used by, or serves the needs of, people who reside in a particular place or region.
-
D.
intendedResidents
Indicates the people or entities for whom a place, dwelling, or facility is designed or meant to be occupied by.
-
E.
hostResidenceOf
Indicates that a location serves as the primary place of residence for a specified person or group.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 29, 2026, 5:23 p.m.