Triple

T7398280
Position Surface form Disambiguated ID Type / Status
Subject Lawrence, Indiana E170679 entity
Predicate hasName P744 FINISHED
Object Lawrence E170679 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: Lawrence | Statement: [Lawrence, Indiana, hasName, Lawrence]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lawrence
Context triple: [Lawrence, Indiana, hasName, Lawrence]
  • A. Lawrence
    Lawrence is a historic mill city in northeastern Massachusetts that developed as a major textile manufacturing center along the Merrimack River.
  • B. Lawrence
    Lawrence is the formal given name of Larry Ellison, the billionaire co-founder and longtime leader of Oracle Corporation.
  • C. Lawrence chosen
    Lawrence is a city located within Marion County in the U.S. state of Indiana.
  • D. Lawrence
    Lawrence is a masculine given name of English origin, derived from the Latin "Laurentius" meaning "from Laurentum" or "crowned with laurel."
  • E. Lawrence
    Lawrence is a college town in northeastern Kansas best known as the home of the University of Kansas and its athletic programs.
  • 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_69c68a5f04188190ac266569c9280347 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f24c1c208190a3d11e816888760d completed March 27, 2026, 9:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69c81106c0788190a3740acf7bb4ab86 completed March 28, 2026, 5:33 p.m.
Created at: March 27, 2026, 3:09 p.m.