Triple
T4178245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lincoln (1217) |
E86529
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Lincoln |
E116393
|
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: [Battle of Lincoln (1217), location, Lincoln]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lincoln Context triple: [Battle of Lincoln (1217), location, Lincoln]
-
A.
Lincoln
Lincoln is a luxury automobile marque of the Ford Motor Company known for its premium sedans and SUVs.
-
B.
Lincoln
Lincoln is a masculine given name of English origin most famously associated with U.S. President Abraham Lincoln.
-
C.
Lincoln
Lincoln is a suburban town in eastern Massachusetts known for its conservation land, historic sites, and commuter access to Boston.
-
D.
Lincoln
chosen
Lincoln is a historic cathedral city in the East Midlands of England, renowned for its medieval architecture, including Lincoln Cathedral and Lincoln Castle.
-
E.
Lincoln
Lincoln is a common English surname most famously associated with U.S. President Abraham Lincoln and his family.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af030114c88190b725908a32ace750 |
completed | March 9, 2026, 5:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b589db323881908ac7c0cd11798c24 |
completed | March 14, 2026, 4:16 p.m. |
Created at: March 9, 2026, 3:45 p.m.