Triple
T17315459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral Rocks |
E420410
|
entity |
| Predicate | hasBestViewFrom |
P9193
|
FINISHED |
| Object | southern end of Jones 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: southern end of Jones Beach | Statement: [Cathedral Rocks, hasBestViewFrom, southern end of Jones Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBestViewFrom Context triple: [Cathedral Rocks, hasBestViewFrom, southern end of Jones Beach]
-
A.
hasScenicViewOf
chosen
Indicates that one entity offers a visually appealing or picturesque view of another entity.
-
B.
hasViewThrough
Indicates that one entity can be seen or visually perceived through another entity acting as an intermediate medium or opening.
-
C.
hasViewingPlatform
Indicates that an entity includes or is equipped with a designated platform or area intended for viewing or observing something.
-
D.
hasViewingSide
Indicates that one entity serves as the side or surface of another entity that is intended to be viewed or observed.
-
E.
hasSummitViewsOf
Indicates that from the summit of one location, there are views overlooking or directed toward another location.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399c6ad88190ba7fcf1d2d53171c |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.