Triple
T9099197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weston Downs |
E218106
|
entity |
| Predicate | hasPrimaryLandmarkType |
P28105
|
FINISHED |
| Object | parks |
—
|
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: parks | Statement: [Weston Downs, hasPrimaryLandmarkType, parks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryLandmarkType Context triple: [Weston Downs, hasPrimaryLandmarkType, parks]
-
A.
isLandmarkFor
Indicates that one entity serves as a notable or significant reference point or attraction for another entity, such as a place, route, or area.
-
B.
hasMainLocationType
chosen
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
-
C.
hasCentralLandmark
Indicates that a place or area contains a primary or defining landmark located at or near its center.
-
D.
isLocalLandmark
Indicates that something is recognized as a notable or significant landmark within a specific local area or community.
-
E.
includesLandmark
Indicates that one location or area contains or encompasses a specific landmark within its boundaries.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9710ac04819096b9c8d3399b9c35 |
completed | April 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.