Triple

T38656405
Position Surface form Disambiguated ID Type / Status
Subject Adair v. United States E939902 entity
Predicate petitioner P3132 FINISHED
Object William Adair
William Adair was the railroad official whose challenge to federal labor regulations led to the landmark 1908 U.S. Supreme Court case Adair v. United States.
E2282760 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: William Adair | Statement: [Adair v. United States, petitioner, William Adair]
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: William Adair
Triple: [Adair v. United States, petitioner, William Adair]
Generated description
William Adair was the railroad official whose challenge to federal labor regulations led to the landmark 1908 U.S. Supreme Court case Adair v. United States.

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_69f76ede49648190a48bfe47032a05a3 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcdbe8c56c8190ab80c9847566fa83 completed May 7, 2026, 6:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4223a750e8819084de22f574074edf completed June 29, 2026, 7:49 a.m.
NEDg Description generation batch_6a42277d406481908744f62d8b6422d5 completed June 29, 2026, 8:06 a.m.
NED2 Entity disambiguation (via description) batch_6a4228885dcc8190ab9202dad1a966f4 completed June 29, 2026, 8:10 a.m.
Created at: May 3, 2026, 4:33 p.m.