Triple
T5265388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windsor Terrace |
E118925
|
entity |
| Predicate | hasParkAccess |
P62705
|
FINISHED |
| Object | Prospect Park Southwest entrances |
—
|
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: Prospect Park Southwest entrances | Statement: [Windsor Terrace, hasParkAccess, Prospect Park Southwest entrances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParkAccess Context triple: [Windsor Terrace, hasParkAccess, Prospect Park Southwest entrances]
-
A.
hasParkStatus
Indicates that an entity holds a particular designation or status related to being a park (e.g., national park, city park, protected parkland).
-
B.
hasParkOwner
Indicates that an entity serves as the owner or legal controller of a particular park.
-
C.
hasParkSection
Indicates that one entity includes, contains, or is associated with a specific section or area of a park.
-
D.
hasParkArea
Indicates that an entity includes or is associated with a designated park or recreational area within its boundaries.
-
E.
hasParking
Indicates that a place or facility provides designated parking space(s) available for use.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7d5906d88190b805977e5a05767a |
completed | March 20, 2026, 5:01 p.m. |
Created at: March 20, 2026, 1:51 p.m.