Triple
T33454434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chase County, Nebraska |
E856732
|
entity |
| Predicate | namedAfterCenturyOfProminence |
P71902
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Chase County, Nebraska, namedAfterCenturyOfProminence, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterCenturyOfProminence Context triple: [Chase County, Nebraska, namedAfterCenturyOfProminence, 19th century]
-
A.
namedAfterCentury
chosen
Indicates that something is named after a specific century, typically reflecting that century’s time period or characteristics.
-
B.
notableFromCentury
Indicates that an entity is notably associated with, or best known from, a particular century.
-
C.
celebratedSinceCentury
Indicates that a celebration, commemoration, or observance of something has been taking place continuously since a specified century.
-
D.
centuryOfGreatestInfluence
Indicates the century during which an entity exerted its greatest impact or influence.
-
E.
popularInCentury
Indicates that something was widely liked, influential, or commonly recognized during a specified century.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 1, 2026, 1:37 a.m.