Triple
T9981932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latourette Golf Course |
E196472
|
entity |
| Predicate | greenSpaceType |
P58534
|
FINISHED |
| Object | urban green space |
—
|
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: urban green space | Statement: [Latourette Golf Course, greenSpaceType, urban green space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: greenSpaceType Context triple: [Latourette Golf Course, greenSpaceType, urban green space]
-
A.
isGreenSpaceType
chosen
Indicates that one entity is classified as a type or category of green space (such as parks, gardens, or natural vegetated areas) in relation to another.
-
B.
isGreenSpaceFor
Indicates that one entity serves as a designated green or open space intended for use or benefit by another entity.
-
C.
landscapeType
Indicates the kind or category of natural terrain or scenery that characterizes a place or area.
-
D.
hasGreenSpaces
Indicates that an entity includes or is associated with areas of vegetation or natural greenery, such as parks, gardens, or lawns.
-
E.
hasNearbyGreenSpace
Indicates that an entity is located close to an area of green space, such as a park, garden, or natural vegetation.
- 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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb8bb3dc481909c65c37303e44037 |
completed | April 2, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:49 p.m.