Triple
T3445659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burlington |
E72669
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Burlington |
unclear NED1
|
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: Burlington | Statement: [Burlington, hasName, Burlington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burlington Context triple: [Burlington, hasName, Burlington]
-
A.
Burlington
Burlington is a historic city in present-day New Jersey that once served as the colonial capital of the Province of New Jersey.
-
B.
Burlington
Burlington is a suburban town in Massachusetts known for its proximity to Boston and its mix of residential neighborhoods, office parks, and retail centers.
-
C.
Burlington
Burlington is a mid-sized city in southern Ontario, Canada, located on the shores of Lake Ontario between Toronto and Hamilton.
-
D.
Burlington
Burlington is a city in North Carolina known historically as a railroad and textile manufacturing hub in the Piedmont region of the state.
-
E.
Burlington
Burlington is a small, primarily residential town in central Connecticut known for its rural character and access to outdoor recreation areas.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba2cc3048190ab1385699387df8d |
completed | March 8, 2026, 6:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b51c5e56b081909794cbab0c3e1cc9 |
completed | March 14, 2026, 8:29 a.m. |
Created at: March 8, 2026, 3:16 p.m.