Triple

T25839512
Position Surface form Disambiguated ID Type / Status
Subject Piscataway peoples E650897 entity
Predicate alternativeName P39 FINISHED
Object Piscataway-Conoy
Piscataway-Conoy refers to a Native American people of the Mid-Atlantic region, historically centered in what is now Maryland along the Chesapeake Bay.
E123044 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: Piscataway-Conoy | Statement: [Piscataway peoples, alternativeName, Piscataway-Conoy]
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: Piscataway-Conoy
Triple: [Piscataway peoples, alternativeName, Piscataway-Conoy]
Generated description
Piscataway-Conoy refers to a Native American people of the Mid-Atlantic region, historically centered in what is now Maryland along the Chesapeake Bay.

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_69e7ab38086081908f3a8e7e0c6efd83 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f601f80b9c8190947c4542654455a6 completed May 2, 2026, 1:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a119a31260c8190bab0e879bb081122 completed May 23, 2026, 12:14 p.m.
NEDg Description generation batch_6a119aa510bc819083c4e8264616f63a completed May 23, 2026, 12:16 p.m.
NED2 Entity disambiguation (via description) batch_6a119b318d4881908d658464d8ea390c completed May 23, 2026, 12:18 p.m.
Created at: April 22, 2026, 7:49 a.m.