Triple

T5591646
Position Surface form Disambiguated ID Type / Status
Subject Lanman E146891 entity
Predicate hasVariant P455 FINISHED
Object Lanmann E146891 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: Lanmann | Statement: [Lanman, hasVariant, Lanmann]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lanmann
Context triple: [Lanman, hasVariant, Lanmann]
  • A. Lanman chosen
    Lanman is a surname most notably associated with American philanthropist William K. Lanman Jr., a major benefactor of Yale University.
  • B. Lahndi
    Lahndi is an Indo-Aryan language (or group of dialects) spoken primarily in western parts of Pakistan, often considered a dialect continuum between Punjabi and Sindhi.
  • C. Luman
    Luman is a masculine given name of English origin, historically borne by figures such as the 19th-century American art patron Luman Reed.
  • D. Barmedman
    Barmedman is a small rural town in the Riverina region of New South Wales, Australia, known historically for its wheat farming and mineral springs.
  • E. Lundie
    Lundie is a small rural settlement in Angus, Scotland, situated near the Sidlaw Hills and known for its scenic countryside setting.
  • 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_69c009036c408190981a8d690b679b67 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c020a3365c8190bd223226c0a6969f completed March 22, 2026, 5:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0286852148190ad4975fe746d7001 completed March 22, 2026, 5:35 p.m.
Created at: March 22, 2026, 3:38 p.m.