Triple
T8709905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Sharpe |
E206747
|
entity |
| Predicate | shoreLengthApprox |
P1568
|
FINISHED |
| Object | 200 miles |
—
|
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: 200 miles | Statement: [Lake Sharpe, shoreLengthApprox, 200 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shoreLengthApprox Context triple: [Lake Sharpe, shoreLengthApprox, 200 miles]
-
A.
shorelineLength
chosen
Indicates the total measured extent of a land area’s boundary where it meets a body of water.
-
B.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
-
C.
hasShoreLengthOn
Indicates that an entity has a specified length of shoreline along or bordering another geographic feature (such as a body of water or coast).
-
D.
hasHighwayAlongShore
Indicates that a highway runs adjacent to or closely follows the shoreline of a body of water.
-
E.
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.
- 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c3034708190b895eaf890d62198 |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.