Triple

T6235434
Position Surface form Disambiguated ID Type / Status
Subject EGXW E139464 entity
Predicate locatedNear P294 FINISHED
Object Lincoln unclear NED1 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: [EGXW, locatedNear, Lincoln]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lincoln
Context triple: [EGXW, locatedNear, Lincoln]
  • A. Lincoln
    Lincoln is a suburban town in eastern Massachusetts known for its conservation land, historic sites, and commuter access to Boston.
  • B. Lincoln
    Lincoln is a luxury automobile marque of the Ford Motor Company known for its premium sedans and SUVs.
  • C. Lincoln
    Lincoln is a common English surname most famously associated with U.S. President Abraham Lincoln and his family.
  • D. Lincoln
    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.
  • E. Lincoln
    Lincoln is a masculine given name of English origin most famously associated with U.S. President Abraham Lincoln.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

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_69c008b0e7ac8190808a59573ee646f3 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c062f236608190997e77b41095883f completed March 22, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69c20df60e488190933b7fa068e96cc4 completed March 24, 2026, 4:07 a.m.
Created at: March 22, 2026, 4:23 p.m.