Triple
T27083278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Arch Rocks |
E685960
|
entity |
| Predicate | formsPartOfView |
P122721
|
FINISHED |
| Object | Oregon Coast Scenic landscape |
—
|
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: Oregon Coast Scenic landscape | Statement: [Three Arch Rocks, formsPartOfView, Oregon Coast Scenic landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsPartOfView Context triple: [Three Arch Rocks, formsPartOfView, Oregon Coast Scenic landscape]
-
A.
isPartOfView
chosen
Indicates that one entity represents a view or perspective that is contained within, derived from, or included as a component of another view or larger visual/contextual structure.
-
B.
structurePartOf
Indicates that one structure is a constituent or component of a larger, encompassing structure.
-
C.
controlsPartOf
Indicates that one entity has authority, influence, or regulatory power over a specific part or subset of another entity.
-
D.
consideredPartOf
Indicates that one entity is regarded or treated as a component, segment, or subset of another entity within a larger whole.
-
E.
isAComponentOf
Indicates that one entity functions as a constituent part or sub-unit of another, larger entity.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 8:36 a.m.