Triple
T8018069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pessac |
E186669
|
entity |
| Predicate | hasTwinTown |
P919
|
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: [Pessac, hasTwinTown, Burlington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burlington Context triple: [Pessac, hasTwinTown, 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 small city in northwestern Washington State known as a commercial hub for the surrounding Skagit Valley region.
-
C.
Burlington
Burlington is a small, primarily residential town in central Connecticut known for its rural character and access to outdoor recreation areas.
-
D.
Burlington
Burlington is a city in northwestern Vermont on the shores of Lake Champlain, known as the state’s largest city and a regional cultural and economic center.
-
E.
Burlington
Burlington is a small town that serves as a local community and commercial center along 3rd Avenue.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df626e8819098a9f8908dfdad3b |
completed | March 31, 2026, 3:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc56c213ec8190b3bd96c42d1357e4 |
completed | March 31, 2026, 11:20 p.m. |
Created at: March 30, 2026, 5:20 p.m.