Triple
T28660596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WPTZ |
E725455
|
entity |
| Predicate | marketServedCity |
P3936
|
FINISHED |
| Object | Burlington, Vermont |
—
|
NE NERFINISHED |
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, Vermont | Statement: [WPTZ, marketServedCity, Burlington, Vermont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketServedCity Context triple: [WPTZ, marketServedCity, Burlington, Vermont]
-
A.
servedCity
chosen
Indicates that a service, route, or facility operates in, reaches, or is available to a particular city.
-
B.
primaryCitiesServed
Indicates the main cities that are directly served or covered by a given entity’s services or operations.
-
C.
alternativeCityServed
Indicates that one city functions as an alternative service location for another city, typically in contexts like transportation or logistics.
-
D.
cityServedRegion
Indicates that a city provides services to, or functions as an administrative or economic center for, a specified region.
-
E.
cityServedType
Indicates the type or category of city that is served by a given entity (such as a facility, service, or infrastructure).
- F. None of above.
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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 4:57 a.m.