Triple
T33456560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Sisters (Oregon) |
E856791
|
entity |
| Predicate | majorLandmarkOf |
P157609
|
FINISHED |
| Object | central Oregon |
—
|
NE NERFINISHED |
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: central Oregon | Statement: [Three Sisters (Oregon), majorLandmarkOf, central Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorLandmarkOf Context triple: [Three Sisters (Oregon), majorLandmarkOf, central Oregon]
-
A.
primaryCityLandmarkOf
Indicates that a landmark is a principal or defining landmark associated with a specific city.
-
B.
cityLandmarkID
Indicates that a specific landmark is uniquely identified as being located within a particular city.
-
C.
knownMonuments
Indicates that an entity is recognized or identified as a monument by another entity or within a given context.
-
D.
isLandmarkNameFor
Indicates that one entity is the name used to identify a particular landmark.
-
E.
isRegionalLandmark
chosen
Indicates that a place or structure is widely recognized as a notable or iconic landmark within a specific geographic region.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 1, 2026, 1:37 a.m.