Triple
T8824902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SG postcode area |
E209989
|
entity |
| Predicate | hasPostTown |
P2711
|
FINISHED |
| Object | Sandy |
E330569
|
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: [SG postcode area, hasPostTown, Sandy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sandy Context triple: [SG postcode area, hasPostTown, 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
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.
Sandy
chosen
Sandy is a small market town in Bedfordshire, England, known historically for its market gardening and proximity to the RSPB headquarters.
-
E.
Sandy
Sandy is a central character in the story featuring Annie, often portrayed as her loyal and beloved dog companion.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc603220508190b64e22dec3ee5ceb |
completed | April 1, 2026, midnight |
| NED1 | Entity disambiguation (via context triple) | batch_69cf894902588190adb60140c64561f6 |
completed | April 3, 2026, 9:32 a.m. |
Created at: March 30, 2026, 6:46 p.m.