Triple
T2467869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broomfield, Colorado |
E55295
|
entity |
| Predicate | becameConsolidatedCityCounty |
P33271
|
FINISHED |
| Object | 2001 |
—
|
LITERAL 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: 2001 | Statement: [Broomfield, Colorado, becameConsolidatedCityCounty, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameConsolidatedCityCounty Context triple: [Broomfield, Colorado, becameConsolidatedCityCounty, 2001]
-
A.
hasConsolidatedCityCountySince
chosen
Indicates that a city and county have been formally consolidated into a single unified government entity starting from a specified point in time.
-
B.
incorporatedAsCity
Indicates that an entity was formally established and legally recognized as a city.
-
C.
countySeatMovedTo
Indicates that the official county seat was relocated from one place to another.
-
D.
existedAsCountyOfDistrictOfColumbiaUntil
Indicates that an entity functioned as a county within the District of Columbia up to a specified end date or time.
-
E.
wasUpgradedToMetropolitanCityIn
Indicates that a city or town was officially elevated in status to a metropolitan city in a specified year or on a specific date.
- 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_69ab49e3622c8190ad22afa2c4fbb807 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2bc7b5481908b3664495e99f1a4 |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0b3ea308190a6d8499c2a542c50 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.