Triple

T16814473
Position Surface form Disambiguated ID Type / Status
Subject Moshassuck River E408705 entity
Predicate flowsThrough P225 FINISHED
Object Lincoln E267903 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: [Moshassuck River, flowsThrough, Lincoln]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lincoln
Context triple: [Moshassuck River, flowsThrough, 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 historic cathedral city in the East Midlands of England, renowned for its medieval architecture, including Lincoln Cathedral and Lincoln Castle.
  • C. Lincoln chosen
    Lincoln is a suburban town in Providence County, Rhode Island, known for its historic mill villages, residential neighborhoods, and recreational areas such as Lincoln Woods State Park.
  • D. Lincoln
    Lincoln is a masculine given name of English origin most famously associated with U.S. President Abraham Lincoln.
  • E. Lincoln
    Lincoln is a small city in Talladega County, Alabama, known for its proximity to the Talladega Superspeedway and Logan Martin Lake.
  • 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_69d88394566c8190b3dcbdc72935f7fa completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b2e0e05081908bd5eaa64abe133d completed April 18, 2026, 4:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00b27dcef481909ccfe4d3d604b1de completed May 10, 2026, 4:29 p.m.
Created at: April 10, 2026, 5:23 a.m.