Triple
T26830877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putney–Mortlake course |
E675495
|
entity |
| Predicate | hasStartLandmark |
P181727
|
FINISHED |
| Object | University Stone at Putney |
—
|
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: University Stone at Putney | Statement: [Putney–Mortlake course, hasStartLandmark, University Stone at Putney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartLandmark Context triple: [Putney–Mortlake course, hasStartLandmark, University Stone at Putney]
-
A.
hasLandmarkAtEnd
Indicates that a landmark is located at the terminal point or end of a specified path, route, or boundary.
-
B.
hasCentralLandmark
Indicates that a place or area contains a primary or defining landmark located at or near its center.
-
C.
hasFormerNearbyLandmark
Indicates that an entity previously had a nearby landmark that no longer exists or no longer holds the same status or relevance.
-
D.
hasLandmarkAtEntrance
Indicates that a specific landmark is located at or directly adjacent to the entrance of something.
-
E.
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.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: April 27, 2026, 5:01 a.m.