Triple
T37915899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schnebly |
E945815
|
entity |
| Predicate | relatedToToponym |
P122228
|
FINISHED |
| Object | Sedona |
E57349
|
NE 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: Sedona | Statement: [Schnebly, relatedToToponym, Sedona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToToponym Context triple: [Schnebly, relatedToToponym, Sedona]
-
A.
hasToponymicAssociation
chosen
Indicates a relationship where one entity is associated with, derived from, or named after a particular place or geographic name (toponym).
-
B.
relatedPlace
Indicates a relationship where one place is connected or associated with another place in a relevant or meaningful way.
-
C.
toponymRefersTo
Indicates that a place name (toponym) designates or refers to a specific geographic entity or location.
-
D.
isToponymOf
Indicates that one entity is a place name (toponym) that refers to the location represented by the other entity.
-
E.
hasToponymicMotivation
Indicates that something is motivated, derived, or named based on a place name (toponym).
- F. None of above.
Provenance (4 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415426838881909d8f68d1952df0e1 |
completed | June 28, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.