Triple
T9200421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harbor Point |
E220822
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Stamford |
E41539
|
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: Stamford | Statement: [Harbor Point, city, Stamford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stamford Context triple: [Harbor Point, city, Stamford]
-
A.
Stamford
Stamford is a historic market town in eastern England renowned for its well-preserved medieval and Georgian architecture.
-
B.
Stamford, Connecticut
chosen
Stamford, Connecticut is a major city in southwestern Connecticut known as a key financial and corporate hub within the New York metropolitan area.
-
C.
West Haven
West Haven is a coastal city in southern Connecticut known for its public beaches and shoreline along Long Island Sound.
-
D.
Hamden
Hamden is a suburban town in south-central Connecticut, known for its proximity to New Haven and as the home of Quinnipiac University.
-
E.
New Haven
New Haven is a small city in central Kentucky known for its historic railroad heritage and proximity to the Kentucky Railway Museum.
- 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_69ca83e8e9248190862cf3e41693b310 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd881c5d48190bbc33fac71a1d849 |
completed | April 1, 2026, 8:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f1658e03a8819098ea2ac2f818a61a |
completed | April 29, 2026, 1:57 a.m. |
Created at: March 30, 2026, 7:25 p.m.