Triple
T24771395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Balkans |
E619731
|
entity |
| Predicate | regionCenter |
P128866
|
FINISHED |
| Object | Pittsburg, Kansas |
—
|
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: Pittsburg, Kansas | Statement: [Little Balkans, regionCenter, Pittsburg, Kansas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCenter Context triple: [Little Balkans, regionCenter, Pittsburg, Kansas]
-
A.
hasRegionCenter
chosen
Indicates that a region is associated with a specific central point or location that serves as its geometric or administrative center.
-
B.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
C.
servesAsRegionalCenterFor
Indicates that one entity functions as the primary administrative, economic, or service hub for a surrounding region or group of entities.
-
D.
metropolitanRegionCenter
Indicates that one location functions as the central or primary hub of a specified metropolitan region.
-
E.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 4:31 a.m.