Triple
T37607463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 430 Park Avenue |
E935692
|
entity |
| Predicate | hasBuildingManagement |
P82333
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [430 Park Avenue, hasBuildingManagement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingManagement Context triple: [430 Park Avenue, hasBuildingManagement, true]
-
A.
hasBuildingOrganization
Indicates that an organization is associated with or occupies a particular building.
-
B.
containsBuilding
Indicates that one location or area includes a building within its boundaries.
-
C.
buildingUseManaged
chosen
Indicates that an entity is responsible for overseeing, controlling, or administering the use or function of a building.
-
D.
hasBuildingStatus
Indicates the current condition, classification, or operational state assigned to a building.
-
E.
hasBuildingServices
Indicates that a building is provided with specific services or utilities by another entity.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:18 p.m.