Triple
T25527092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glen Eyrie estate |
E639804
|
entity |
| Predicate | ownerRoleInCity |
P8234
|
FINISHED |
| Object | founder of Colorado Springs |
—
|
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: founder of Colorado Springs | Statement: [Glen Eyrie estate, ownerRoleInCity, founder of Colorado Springs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerRoleInCity Context triple: [Glen Eyrie estate, ownerRoleInCity, founder of Colorado Springs]
-
A.
hasCityRole
chosen
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
B.
hasCityRight
Indicates that an entity possesses legal or official rights associated with a particular city, such as jurisdiction, privileges, or authority within that city.
-
C.
hasUrbanRole
Indicates that an entity plays a specific functional or social role within an urban or city context.
-
D.
cityOwned
Indicates that something is owned, managed, or under the jurisdiction of a city or municipal government.
-
E.
isInCity
Indicates that one entity is located within the geographical boundaries of a specified city.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f86073d0819093afb1d79b97bccc |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 3:11 p.m.