Triple
T36721795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berthoud, Colorado |
E907082
|
entity |
| Predicate | hasPlanningIdentity |
P73280
|
FINISHED |
| Object | historic downtown core |
—
|
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: historic downtown core | Statement: [Berthoud, Colorado, hasPlanningIdentity, historic downtown core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningIdentity Context triple: [Berthoud, Colorado, hasPlanningIdentity, historic downtown core]
-
A.
planningIdentity
chosen
Indicates that an entity serves as the specific identity or role under which planning or plan-related activities are carried out.
-
B.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
C.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
D.
hasPlanningAssociation
Indicates a relationship where one entity is involved with, linked to, or considered in the planning or preparation activities of another entity.
-
E.
hasPlanningCharacteristic
Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 3, 2026, 4:12 p.m.