Triple
T10865245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunnyside Yard |
E256509
|
entity |
| Predicate | hasProposal |
P96136
|
FINISHED |
| Object | overbuild mixed-use development |
—
|
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: overbuild mixed-use development | Statement: [Sunnyside Yard, hasProposal, overbuild mixed-use development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProposal Context triple: [Sunnyside Yard, hasProposal, overbuild mixed-use development]
-
A.
hasProposedResolution
Indicates that an entity has put forward a specific resolution or solution for consideration or decision regarding another entity or issue.
-
B.
hasBridgeProposal
Indicates that there is a proposed plan or suggestion to build or establish a bridge between the related entities.
-
C.
proposalType
Indicates the specific category or kind of proposal associated with an entity or event.
-
D.
hasProposedRole
Indicates that one entity has suggested or put forward a specific role or position for another entity.
-
E.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7516b2f148190adbacd35fc8c2056 |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:20 p.m.