Triple
T5700661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annapolis Historic District |
E125650
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Spa Creek |
E727158
|
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: Spa Creek | Statement: [Annapolis Historic District, near, Spa Creek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Spa Creek Context triple: [Annapolis Historic District, near, Spa Creek]
-
A.
Spa Creek
chosen
Spa Creek is a tidal inlet and waterway in Annapolis, Maryland, known for its marinas, boating activity, and proximity to the historic downtown and U.S. Naval Academy.
-
B.
Spruce Creek
Spruce Creek is a small tidal waterway in southern Maine that flows through the town of Kittery before emptying into the Piscataqua River.
-
C.
Hunting Creek
Hunting Creek is a smaller stream in North Carolina that feeds into the Yadkin River as one of its tributaries.
-
D.
Richland Creek
Richland Creek is a waterway in southern Tennessee that flows through the city of Pulaski and the surrounding Giles County region.
-
E.
Swamp Creek
Swamp Creek is a smaller stream in Pennsylvania that feeds into Perkiomen Creek as part of the Schuylkill River watershed.
- 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_69c0082c96988190b3a6a201edce472a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c024540afc8190aee3760f71ea39c2 |
completed | March 22, 2026, 5:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffd37b54881908c67d5746f9ef39e |
completed | April 3, 2026, 5:47 p.m. |
Created at: March 22, 2026, 3:45 p.m.