Triple

T21497336
Position Surface form Disambiguated ID Type / Status
Subject Peter Muhlenberg E530388 entity
Predicate familyName P18 FINISHED
Object Muhlenberg E146748 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: Muhlenberg | Statement: [Peter Muhlenberg, familyName, Muhlenberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Muhlenberg
Context triple: [Peter Muhlenberg, familyName, Muhlenberg]
  • A. Muhlenberg chosen
    Muhlenberg is a German-origin surname notably associated with the influential American Muhlenberg family, including early political and religious leaders in the United States.
  • B. Ligonier
    Ligonier is a small historic borough in Pennsylvania known for its picturesque town square, frontier-era fort, and role as a gateway to the Laurel Highlands region.
  • C. Gustavus
    Gustavus is a Latinized masculine given name historically borne by several Swedish kings and used in various European and English-speaking contexts.
  • D. Sagamore
    Sagamore is a village in the town of Bourne on Cape Cod, Massachusetts, known as a gateway community near the Cape Cod Canal.
  • E. Duquesne
    Duquesne is a French noble family name historically associated with military and colonial leadership, notably in 18th-century New France.
  • 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_69e0c45bd15481909fba5910765cdda2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9ea58faa08190ab9f60b0db3c425b completed April 23, 2026, 9:46 a.m.
NED1 Entity disambiguation (via context triple) batch_6a09e13d6bc88190a55f46c68c9c55c2 completed May 17, 2026, 3:39 p.m.
Created at: April 16, 2026, 6:23 p.m.