Triple
T11521637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goddard Memorial State Park |
E273175
|
entity |
| Predicate | hasLengthOfShoreline |
P1568
|
FINISHED |
| Object | approximately 18 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: approximately 18 miles | Statement: [Goddard Memorial State Park, hasLengthOfShoreline, approximately 18 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLengthOfShoreline Context triple: [Goddard Memorial State Park, hasLengthOfShoreline, approximately 18 miles]
-
A.
shorelineLength
chosen
Indicates the total measured extent of a land area’s boundary where it meets a body of water.
-
B.
hasLongShoreline
Indicates that an entity possesses an extensive or unusually long shoreline relative to typical cases.
-
C.
hasCoastlineLengthApprox
Indicates an approximate measurement of the total length of an entity’s coastline.
-
D.
hasCoastlineLengthRank
Indicates the relative position of an entity in an ordered ranking based on the length of its coastline.
-
E.
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).
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fd129c88190893b95222480e04a |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.