Triple
T23851818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binigaus |
E592189
|
entity |
| Predicate | hasShoreWidth |
P6651
|
FINISHED |
| Object | wide sandy shore |
—
|
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: wide sandy shore | Statement: [Binigaus, hasShoreWidth, wide sandy shore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShoreWidth Context triple: [Binigaus, hasShoreWidth, wide sandy shore]
-
A.
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).
-
B.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
C.
hasShoreLengthUnit
Indicates the unit of measurement used to express the length of a shore or coastline.
-
D.
hasShoreFeature
chosen
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
E.
hasShoreOrientation
Indicates the directional orientation of a shoreline relative to a reference frame (e.g., compass direction or facing).
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c987c3208190bf3f210d12106927 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.