Triple
T36654171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delicate Arch Viewpoint |
E904944
|
entity |
| Predicate | hasSubjectOfInterest |
P494
|
FINISHED |
| Object | natural sandstone arch |
—
|
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: natural sandstone arch | Statement: [Delicate Arch Viewpoint, hasSubjectOfInterest, natural sandstone arch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectOfInterest Context triple: [Delicate Arch Viewpoint, hasSubjectOfInterest, natural sandstone arch]
-
A.
hasAreaOfInterest
Indicates that an entity possesses or is associated with a particular area of interest or focus.
-
B.
hasHumanInterest
Indicates that something is of particular relevance, appeal, or concern to people, often engaging their emotions, curiosity, or personal experiences.
-
C.
hasNotableSubject
chosen
Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
-
D.
hasBeenSubjectOf
Indicates that an entity has previously been the focus or target of a particular action, process, or investigation.
-
E.
hasHumanSubject
Indicates that an entity serves as the human participant or subject involved in an action, event, or relation.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00262d71488190a769783fb09e5803 |
completed | May 10, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_6a0023985f148190a335a3fb93e9981e |
completed | May 10, 2026, 6:20 a.m. |
Created at: May 3, 2026, 4:11 p.m.