Triple

T19418668
Position Surface form Disambiguated ID Type / Status
Subject Plum, Pennsylvania E485786 entity
Predicate namedAfter P63 FINISHED
Object Plum Creek
Plum Creek is a waterway in Pennsylvania historically significant enough to lend its name to the nearby borough of Plum.
E1388473 NE FINISHED

How this triple was built (4 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: Plum Creek | Statement: [Plum, Pennsylvania, namedAfter, Plum Creek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Plum Creek
Context triple: [Plum, Pennsylvania, namedAfter, Plum Creek]
  • A. Plum Creek
    Plum Creek is a stream in central Texas known for its historical significance in early Texas frontier conflicts and settlement.
  • B. Plum Creek
    Plum Creek is a smaller stream in North America that serves as a tributary feeding into the Souris River.
  • C. Skunk Creek
    Skunk Creek is a smaller stream in the north-central United States that serves as a tributary feeding into the Big Sioux River.
  • D. Banning Creek
    Banning Creek is a stream in Arizona that serves as the primary inflow to Goldwater Lake near Prescott.
  • E. Blaine Creek
    Blaine Creek is a smaller waterway in Oregon that feeds into the Nestucca River, contributing to the river’s flow and local watershed.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Plum Creek
Triple: [Plum, Pennsylvania, namedAfter, Plum Creek]
Generated description
Plum Creek is a waterway in Pennsylvania historically significant enough to lend its name to the nearby borough of Plum.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Plum Creek
Target entity description: Plum Creek is a waterway in Pennsylvania historically significant enough to lend its name to the nearby borough of Plum.
  • A. Plum Creek
    Plum Creek is a stream in central Texas known for its historical significance in early Texas frontier conflicts and settlement.
  • B. Plum Creek
    Plum Creek is a smaller stream in North America that serves as a tributary feeding into the Souris River.
  • C. Skunk Creek
    Skunk Creek is a smaller stream in the north-central United States that serves as a tributary feeding into the Big Sioux River.
  • D. Banning Creek
    Banning Creek is a stream in Arizona that serves as the primary inflow to Goldwater Lake near Prescott.
  • E. Blaine Creek
    Blaine Creek is a smaller waterway in Oregon that feeds into the Nestucca River, contributing to the river’s flow and local watershed.
  • F. None of above. chosen

Provenance (5 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_69d8e8d688f881909c85104a62e09d8a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62afbaf0c8190913eda4b04efbe67 completed April 20, 2026, 1:32 p.m.
NED1 Entity disambiguation (via context triple) batch_6a077ecff70881908bf689e600bcb2fe completed May 15, 2026, 8:15 p.m.
NEDg Description generation batch_6a077fcef0288190a6c82be17c29a4ae completed May 15, 2026, 8:19 p.m.
NED2 Entity disambiguation (via description) batch_6a0780a281248190a1056b682f0aa952 completed May 15, 2026, 8:22 p.m.
Created at: April 10, 2026, 1:37 p.m.