Triple

T13172159
Position Surface form Disambiguated ID Type / Status
Subject Gretna, Virginia E313002 entity
Predicate hasName P744 FINISHED
Object Gretna E313002 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: Gretna | Statement: [Gretna, Virginia, hasName, Gretna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gretna
Context triple: [Gretna, Virginia, hasName, Gretna]
  • A. Gretna
    Gretna is a small but rapidly growing city in eastern Nebraska, known for its convenient location near Omaha and attractions like the Nebraska Crossing outlet mall.
  • B. Gretna
    Gretna is a small Scottish town near the England–Scotland border, historically famous as a destination for runaway weddings.
  • C. Gretna, Louisiana
    Gretna, Louisiana is a small city in Jefferson Parish, part of the New Orleans metropolitan area, known as a local governmental and judicial center.
  • D. Gretna, Virginia chosen
    Gretna, Virginia is a small incorporated town in southern Virginia known for its rural character and location within Pittsylvania County.
  • E. Covington
    Covington is a city in the Atlanta metropolitan area of Georgia, known for its historic town square and frequent use as a filming location for movies and television shows.
  • 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_69d806ac3ee081909b2fd27d060aa974 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98c2f22b881908a0af3af0a0af971 completed April 10, 2026, 11:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69f70a2a3f2881909af3e146ee24062d completed May 3, 2026, 8:41 a.m.
Created at: April 9, 2026, 9:13 p.m.