Triple
T36789769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC3: Incremental Construction of Inductive Clauses for Indubitable Correctness |
E909017
|
entity |
| Predicate | verificationDomain |
P186553
|
FINISHED |
| Object | bit-level hardware verification |
—
|
LITERAL 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: bit-level hardware verification | Statement: [IC3: Incremental Construction of Inductive Clauses for Indubitable Correctness, verificationDomain, bit-level hardware verification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verificationDomain Context triple: [IC3: Incremental Construction of Inductive Clauses for Indubitable Correctness, verificationDomain, bit-level hardware verification]
-
A.
verificationTarget
Indicates that one entity is the object, subject, or content that another entity is intended to verify or validate.
-
B.
verificationBasis
Indicates the underlying evidence, method, or criteria used to confirm or validate that something is true, correct, or compliant.
-
C.
verificationDevice
Indicates that one entity functions as a device used to verify, authenticate, or confirm the status or properties of another entity.
-
D.
verificationStatus
Indicates whether an entity, claim, or item has been checked and confirmed as authentic, accurate, or compliant according to a defined verification process.
-
E.
verificationUsedBy
Indicates that a particular verification method, process, or artifact is employed or relied upon by a specified entity or system.
- F. None of above. chosen
Provenance (4 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_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:12 p.m.