Triple
T19705690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zlatni Rat |
E473207
|
entity |
| Predicate | shorelineOrientation |
P91974
|
FINISHED |
| Object | changes with currents and winds |
—
|
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: changes with currents and winds | Statement: [Zlatni Rat, shorelineOrientation, changes with currents and winds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shorelineOrientation Context triple: [Zlatni Rat, shorelineOrientation, changes with currents and winds]
-
A.
coastOrientation
Indicates the directional alignment or facing direction of a coastline relative to the cardinal or geographic axes.
-
B.
hasShoreOrientation
chosen
Indicates the directional orientation of a shoreline relative to a reference frame (e.g., compass direction or facing).
-
C.
shorelineCharacteristic
Indicates the specific physical or environmental qualities that describe the nature or condition of a shoreline in relation to another entity.
-
D.
oceanOrientation
Indicates the directional alignment or facing of something relative to an ocean.
-
E.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642ba4bd08190b016b8c6664079c4 |
completed | April 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.