Triple
T5761438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yavapai County Courthouse |
E127102
|
entity |
| Predicate | locationCityCenter |
P25976
|
FINISHED |
| Object | downtown Prescott |
—
|
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: downtown Prescott | Statement: [Yavapai County Courthouse, locationCityCenter, downtown Prescott]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationCityCenter Context triple: [Yavapai County Courthouse, locationCityCenter, downtown Prescott]
-
A.
notableCityCenter
Indicates that a location serves as a prominent or significant central area within a city.
-
B.
hasCityCentreLocation
chosen
Indicates that something is located in, or directly associated with, the central area of a city.
-
C.
hasPopulationCenter
Indicates that an area, region, or administrative unit contains or is served by a primary settlement or population hub.
-
D.
cityLocatedIn
Indicates that a city is geographically situated within a specified larger administrative or territorial region.
-
E.
capitalLocation
Indicates the relationship in which a place serves as the capital city or administrative center of a given political or geographic entity.
- 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02939b22c81908f8354ab175d168d |
completed | March 22, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.