Triple
T26830878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putney–Mortlake course |
E675495
|
entity |
| Predicate | hasFinishLandmark |
P79515
|
FINISHED |
| Object | Mortlake Brewery area |
—
|
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: Mortlake Brewery area | Statement: [Putney–Mortlake course, hasFinishLandmark, Mortlake Brewery area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinishLandmark Context triple: [Putney–Mortlake course, hasFinishLandmark, Mortlake Brewery area]
-
A.
hasLandmarkAtEnd
chosen
Indicates that a landmark is located at the terminal point or end of a specified path, route, or boundary.
-
B.
hasLandmarkStatusIn
Indicates that an entity holds a recognized landmark status within a specified geographic or administrative area.
-
C.
hasLandmarkStatusFrom
Indicates that an entity has been granted a specific landmark status by a particular authority, source, or designation system.
-
D.
hasFinishTown
Indicates that an entity has a town where an event, process, or journey concludes or is completed.
-
E.
hasReach
Indicates that one entity is able to extend its influence, access, or physical span to another entity or area.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 27, 2026, 5:01 a.m.