Triple
T11772950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sedona Arts Festival |
E279943
|
entity |
| Predicate | cityKnownFor |
P24465
|
FINISHED |
| Object | red rock formations |
—
|
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: red rock formations | Statement: [Sedona Arts Festival, cityKnownFor, red rock formations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityKnownFor Context triple: [Sedona Arts Festival, cityKnownFor, red rock formations]
-
A.
primaryCityLandmarkOf
Indicates that a landmark is a principal or defining landmark associated with a specific city.
-
B.
cityRecognizedBy
Indicates that a city has been formally acknowledged, certified, or granted status by a particular authority, organization, or governing body.
-
C.
hasFamousCity
Indicates that an entity possesses or is associated with a city that is widely recognized or renowned.
-
D.
cityAssociatedWith
chosen
Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
-
E.
citySymbolOf
Indicates that a particular city serves as an official symbol or emblem representing another entity, such as a region, organization, or concept.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:41 p.m.