Triple
T28752212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 CNN Money "100 Best Places to Live" list |
E731561
|
entity |
| Predicate | rankingCount |
P136945
|
FINISHED |
| Object | 100 |
—
|
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: 100 | Statement: [2005 CNN Money "100 Best Places to Live" list, rankingCount, 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingCount Context triple: [2005 CNN Money "100 Best Places to Live" list, rankingCount, 100]
-
A.
rankingUsage
Indicates how an entity is used or positioned within an ordered ranking or hierarchy relative to others.
-
B.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
C.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
D.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
E.
rankComparedToCount
chosen
Indicates how an entity’s rank or ordering position compares relative to a specified total count or number of items.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 6:08 a.m.