Triple
T9838503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symbolic Model Checking |
E239161
|
entity |
| Predicate | verificationTarget |
P90263
|
FINISHED |
| Object | finite-state systems |
—
|
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: finite-state systems | Statement: [Symbolic Model Checking, verificationTarget, finite-state systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verificationTarget Context triple: [Symbolic Model Checking, verificationTarget, finite-state systems]
-
A.
verificationSystem
Indicates that an entity functions as or is associated with a system responsible for checking, validating, or confirming the correctness or authenticity of something.
-
B.
verificationStatus
Indicates whether an entity, claim, or item has been checked and confirmed as authentic, accurate, or compliant according to a defined verification process.
-
C.
confirmationMethod
Indicates the means or process by which something is verified, validated, or confirmed as true or accepted.
-
D.
dataTypeVerified
Indicates that the data’s type has been checked and confirmed to match the expected or required type.
-
E.
confirmationRequirement
Indicates that an action, decision, or change is contingent on receiving explicit confirmation from a specified party or process.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34921b881909836ba0f5b42a27b |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:33 p.m.