Triple
T24065294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1 Wall Street |
E596070
|
entity |
| Predicate | developerForConversion |
P48253
|
FINISHED |
| Object | Macklowe Properties |
—
|
NE NERFINISHED |
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: Macklowe Properties | Statement: [1 Wall Street, developerForConversion, Macklowe Properties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerForConversion Context triple: [1 Wall Street, developerForConversion, Macklowe Properties]
-
A.
conversionProcess
Indicates a process in which something is transformed or changed from one state, form, or representation into another.
-
B.
conversionWave
Indicates a process in which changes or transformations spread through entities or states in a sequential, wave-like manner.
-
C.
toolDeveloperFor
Indicates that one entity is the creator or developer of a tool that is used by or associated with another entity.
-
D.
platformDeveloper
Indicates that one entity is the developer or creator responsible for building or maintaining the other entity as a platform.
-
E.
developmentAffiliateFor
chosen
Indicates that one entity serves as a development-related affiliate, partner, or associated organization for 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da5aa1a48190afec72bbcfd379c3 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:40 p.m.