Triple
T16773471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Champlain Towers South condominium |
E407661
|
entity |
| Predicate | proximityToShoreline |
P16235
|
FINISHED |
| Object | directly adjacent to beach |
—
|
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: directly adjacent to beach | Statement: [Champlain Towers South condominium, proximityToShoreline, directly adjacent to beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proximityToShoreline Context triple: [Champlain Towers South condominium, proximityToShoreline, directly adjacent to beach]
-
A.
distanceFromCoast
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
B.
stateOnNearestShore
Indicates that an entity is located on the shore that is geographically closest to another specified reference point or entity.
-
C.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
D.
nearIsland
Indicates that one entity is located close to or in the vicinity of an island.
-
E.
positionRelativeToCoast
chosen
Indicates the spatial relationship of something to a coastline, such as its distance or orientation relative to the 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b037c5708190ba604e7707b5a8a2 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.