Triple
T21241351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Saint Nicholas in Nimporio |
E523480
|
entity |
| Predicate | locationRelativeToSea |
P16235
|
FINISHED |
| Object | seaside |
—
|
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: seaside | Statement: [Church of Saint Nicholas in Nimporio, locationRelativeToSea, seaside]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRelativeToSea Context triple: [Church of Saint Nicholas in Nimporio, locationRelativeToSea, seaside]
-
A.
positionRelativeToCoast
chosen
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the coast.
-
B.
oceanLocation
Indicates that one entity is geographically located in, on, or adjacent to a particular ocean.
-
C.
hasElevationRelativeToSeaLevel
Indicates the elevation or height of an entity measured relative to mean sea level.
-
D.
positionRelativeToSurfaceCurrents
Indicates the spatial relationship of an entity’s location or movement with respect to the direction and pattern of surface currents.
-
E.
positionRelativeToTide
Indicates the spatial relationship of something’s location with respect to the current or expected tide level or tidal zone.
- 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735239f48819091ffe518b1aed2e8 |
completed | April 21, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:47 p.m.