Triple

T36789684

Position	Surface form	Disambiguated ID	Type / Status
Subject	IC3 model checking algorithm	`E909016`	entity
Predicate	acronym	`P43`	FINISHED
Object	IC3 IC3 is a SAT-based model checking algorithm used for efficiently verifying safety properties of hardware and software systems by incrementally constructing inductive invariants.	`E2199508`	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: IC3 | Statement: [IC3 model checking algorithm, acronym, IC3]

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: IC3
Triple: [IC3 model checking algorithm, acronym, IC3]

Generated description

IC3 is a SAT-based model checking algorithm used for efficiently verifying safety properties of hardware and software systems by incrementally constructing inductive invariants.

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_69f76e7a937c81909ed7359641e670f6`	completed	May 3, 2026, 3:49 p.m.
NER	Named-entity recognition	`batch_69f7c9fd7ee081908faacc427cd200fe`	completed	May 3, 2026, 10:19 p.m.
NED1	Entity disambiguation (via context triple)	`batch_6a3d17a7e32081909273c276a7a087c2`	completed	June 25, 2026, 11:57 a.m.
NEDg	Description generation	`batch_6a3d22caef88819084e4c278d7a5b7ee`	completed	June 25, 2026, 12:44 p.m.
NED2	Entity disambiguation (via description)	`batch_6a3d715a991c8190b130e11d62a2c451`	completed	June 25, 2026, 6:20 p.m.

Created at: May 3, 2026, 4:12 p.m.