Triple
T14019351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado State Capitol |
E337285
|
entity |
| Predicate | stateSymbol |
P96057
|
FINISHED |
| Object | symbol of Colorado government |
—
|
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: symbol of Colorado government | Statement: [Colorado State Capitol, stateSymbol, symbol of Colorado government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateSymbol Context triple: [Colorado State Capitol, stateSymbol, symbol of Colorado government]
-
A.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
-
B.
stateName
Indicates that an entity is identified by or associated with a particular state’s name.
-
C.
USStateSymbolOf
chosen
Indicates that something is officially designated as a symbolic representation (such as a bird, flower, or motto) of a particular U.S. state.
-
D.
stateNickname
Indicates that one entity is the commonly used nickname or informal moniker for a given state.
-
E.
states
Indicates that an entity formally declares, expresses, or asserts a fact, opinion, or condition about another entity or situation.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3b5b088190a58715779d2c46a6 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.