Triple
T33140182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Katherine |
E848124
|
entity |
| Predicate | accessViaTrail |
P93497
|
FINISHED |
| Object | Winsor Trail |
—
|
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: Winsor Trail | Statement: [Lake Katherine, accessViaTrail, Winsor Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessViaTrail Context triple: [Lake Katherine, accessViaTrail, Winsor Trail]
-
A.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
-
B.
hasTrailAccessPoint
chosen
Indicates that there is a specific access point or entrance connecting a location to a trail or pathway.
-
C.
trailheadAccessRoad
Indicates the road that provides access to a specific trailhead.
-
D.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
E.
trailOpened
Indicates that a trail has been made available for use or access, typically after being closed or not yet established.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:28 a.m.