Triple
T27301348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter Peak |
E688915
|
entity |
| Predicate | hasSheepStation |
P168080
|
FINISHED |
| Object | Walter Peak High Country Farm |
—
|
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: Walter Peak High Country Farm | Statement: [Walter Peak, hasSheepStation, Walter Peak High Country Farm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSheepStation Context triple: [Walter Peak, hasSheepStation, Walter Peak High Country Farm]
-
A.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
-
B.
hasStations
Indicates that one entity possesses, contains, or is associated with one or more stations.
-
C.
hasEndpointStation
Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
-
D.
hasStationFunction
Indicates that an entity serves in a particular functional role or capacity at a station.
-
E.
hasStationNear
Indicates that one entity has a station located in close proximity to another entity.
- 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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 27, 2026, 11:22 a.m.