Triple
T25385493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silvermine Lake |
E631510
|
entity |
| Predicate | accessibleFromRoad |
P22549
|
FINISHED |
| Object | Seven Lakes Drive |
—
|
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: Seven Lakes Drive | Statement: [Silvermine Lake, accessibleFromRoad, Seven Lakes Drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessibleFromRoad Context triple: [Silvermine Lake, accessibleFromRoad, Seven Lakes Drive]
-
A.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
B.
hasSeparateAccessRoadFor
Indicates that one entity is served by its own distinct access road that is separate from the access road used by another entity.
-
C.
hasSeparateAccessRoad
Indicates that an entity is served by its own distinct access road, separate from other routes or shared entrances.
-
D.
hasNoDirectRoadAccess
Indicates that there is no direct road connection available between the relevant locations or entities.
-
E.
roadAccessFrom
chosen
Indicates that one location can be reached from another via a usable road connection.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 1:46 p.m.