Triple
T7626504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln County, Kansas |
E172646
|
entity |
| Predicate | largestCity |
P235
|
FINISHED |
| Object | Lincoln |
E677451
|
NE 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: Lincoln | Statement: [Lincoln County, Kansas, largestCity, Lincoln]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lincoln Context triple: [Lincoln County, Kansas, largestCity, Lincoln]
-
A.
Lincoln
Lincoln is a historic cathedral city in the East Midlands of England, renowned for its medieval architecture, including Lincoln Cathedral and Lincoln Castle.
-
B.
Lincoln
Lincoln is a common English surname most famously associated with U.S. President Abraham Lincoln and his family.
-
C.
Lincoln
Lincoln is a masculine given name of English origin most famously associated with U.S. President Abraham Lincoln.
-
D.
Lincoln
Lincoln is a historic American city in Illinois best known as the namesake of President Abraham Lincoln and for its rich Civil War–era heritage.
-
E.
Lincoln
chosen
Lincoln is a small city in north-central Kansas that serves as the administrative and economic hub of Lincoln County.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa8150ac8190908aec411b0f4e50 |
completed | March 27, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8a212d0888190a40cdf32ef53d993 |
completed | March 29, 2026, 3:52 a.m. |
Created at: March 27, 2026, 3:56 p.m.