Triple
T30793222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 28 (Nevada) |
E784156
|
entity |
| Predicate | shoreSection |
P26675
|
FINISHED |
| Object | northeastern shore of Lake Tahoe |
—
|
LITERAL FINISHED |
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: northeastern shore of Lake Tahoe | Statement: [SR 28 (Nevada), shoreSection, northeastern shore of Lake Tahoe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoreSection Context triple: [SR 28 (Nevada), shoreSection, northeastern shore of Lake Tahoe]
-
A.
shoreHas
Indicates that a shore possesses, contains, or is characterized by a particular feature, object, or attribute.
-
B.
shore
Indicates a relationship where one entity forms or lies along the edge or boundary of a body of water, such as a sea, lake, or river.
-
C.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
D.
shorelineIncludes
chosen
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
-
E.
shorelineOwnership
Indicates that one entity holds legal or recognized ownership rights over a stretch of shoreline associated with another entity or location.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6901035b88190ba857258707694cf |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:42 p.m.