Triple
T30053833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CU |
E763672
|
entity |
| Predicate | systemHeadquartersLocation |
P173408
|
FINISHED |
| Object | Boulder, Colorado |
—
|
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: Boulder, Colorado | Statement: [CU, systemHeadquartersLocation, Boulder, Colorado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemHeadquartersLocation Context triple: [CU, systemHeadquartersLocation, Boulder, Colorado]
-
A.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
B.
campaignHeadquartersLocation
Indicates the specific place where a political or organizational campaign’s main headquarters is located.
-
C.
serviceBranchHeadquarters
Indicates the location that serves as the main headquarters for a particular military or service branch.
-
D.
employerHeadquarters
Indicates the location where an employer’s main corporate offices or central administrative operations are based.
-
E.
headquartersSuccessorOrganizationLocation
Indicates that the location served as the headquarters for a successor organization that followed a previous entity.
- F. None of above. chosen
Provenance (4 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 29, 2026, 6:56 p.m.