Triple

T19375514
Position Surface form Disambiguated ID Type / Status
Subject Morse family E484655 entity
Predicate linkedTo P37 FINISHED
Object Libby family NE NERFINISHED

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: Libby family | Statement: [Morse family, linkedTo, Libby family]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Libby family
Context triple: [Morse family, linkedTo, Libby family]
  • A. Libby family chosen
    The Libby family was a prominent 19th-century Portland, Maine family whose wealth from the dry-goods trade helped shape the city’s social and architectural history.
  • B. Lindsay family
    The Lindsay family is a prominent Scottish noble lineage historically associated with the Earls of Crawford and Glenesk.
  • C. Greg family
    The Greg family was a prominent British industrialist and merchant dynasty influential in the development of the textile industry during the Industrial Revolution.
  • D. Moffatt family
    The Moffatt family was a prominent colonial-era New England merchant family associated with wealth, trade, and social influence, particularly in Portsmouth, New Hampshire.
  • E. Bell family
    The Bell family is a prominent local lineage historically associated with Bellport, New York, for whom the village was named.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d460d88190abf0591c5c9d2b0c completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e61a5c05c08190b91cb32fdb79813b completed April 20, 2026, 12:21 p.m.
Created at: April 10, 2026, 1:35 p.m.