Triple
T31233754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest Hills, Queens |
E796356
|
entity |
| Predicate | servedByPark |
P62478
|
FINISHED |
| Object | Forest Park |
—
|
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: Forest Park | Statement: [Forest Hills, Queens, servedByPark, Forest Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByPark Context triple: [Forest Hills, Queens, servedByPark, Forest Park]
-
A.
parkServed
Indicates that a particular park is provided with services or coverage by a specified entity (such as a transit line, facility, or administrative body).
-
B.
servicePark
Indicates that one entity serves as a designated area or facility where vehicles or equipment are parked, maintained, or serviced in relation to another entity.
-
C.
inPark
Indicates that one entity is located within or inside the boundaries of a park.
-
D.
servesAttraction
Indicates that one entity functions as or provides a service that supports or enhances the experience of a particular attraction.
-
E.
associatedWithPark
chosen
Indicates a relationship in which an entity is connected or linked in some relevant way to a particular park.
- 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: April 29, 2026, 9:10 p.m.