Triple
T1873851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wasatch Front |
E39094
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Sandy |
E187767
|
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: Sandy | Statement: [Wasatch Front, hasCity, Sandy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sandy Context triple: [Wasatch Front, hasCity, Sandy]
-
A.
Sandy
Sandy is a common nickname or short form of the given name Alexander.
-
B.
Sandy
Sandy is a fictional character from Mark Twain’s satirical novel "A Connecticut Yankee in King Arthur’s Court," known as a medieval woman who becomes the companion and later wife of the time-traveling protagonist.
-
C.
Sandy
chosen
Sandy is a suburban city in the Salt Lake City metropolitan area of Utah, known for its residential communities and proximity to outdoor recreation in the nearby Wasatch Mountains.
-
D.
Sandi
Sandi is a given name, typically a variant of Sandy, used for both males and females.
-
E.
Sandy-boy
Sandy-boy is a diminutive or affectionate nickname derived from the given name Sandy.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0d648ec8190a21445ddca6f9aa6 |
completed | March 7, 2026, 5 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69addf5419488190ad96110f6ac7111f |
completed | March 8, 2026, 8:43 p.m. |
Created at: March 4, 2026, 7:34 p.m.