Triple
T634911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overland Park, Kansas |
E16601
|
entity |
| Predicate | awardOrRanking |
P17372
|
FINISHED |
| Object | frequently listed among best places to live in the United States |
—
|
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: frequently listed among best places to live in the United States | Statement: [Overland Park, Kansas, awardOrRanking, frequently listed among best places to live in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardOrRanking Context triple: [Overland Park, Kansas, awardOrRanking, frequently listed among best places to live in the United States]
-
A.
awardType
Indicates the specific category or kind of award associated with an entity or event.
-
B.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
-
C.
awardName
Indicates the specific name or title of an award associated with an entity.
-
D.
awardClass
Indicates the classification or category assigned to an award within an award-giving system.
-
E.
awardReceived
Indicates that an entity has been granted or honored with a specific award or recognition.
- F. None of above. chosen
Provenance (4 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ee4ee8481908ad45405e3f3835c |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d0483908190a5ec42a7403c258e |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49defe58c8190bd39ef47c9f660a7 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.