Triple
T31136971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Bay |
E793671
|
entity |
| Predicate | hasShorelineCharacter |
P6651
|
FINISHED |
| Object | quiet shoreline |
—
|
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: quiet shoreline | Statement: [North Bay, hasShorelineCharacter, quiet shoreline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShorelineCharacter Context triple: [North Bay, hasShorelineCharacter, quiet shoreline]
-
A.
hasShoreFeature
chosen
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
B.
hasShorelineMarker
Indicates that a location or area is marked or delineated by a designated shoreline indicator or boundary marker.
-
C.
hasShorelineMaterial
Indicates that a geographic feature’s shoreline is composed of or characterized by a specified material.
-
D.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
E.
hasShorelineUse
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 9:05 p.m.