Triple
T9838507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symbolic Model Checking |
E239161
|
entity |
| Predicate | checksPropertyType |
P9380
|
FINISHED |
| Object | safety properties |
—
|
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: safety properties | Statement: [Symbolic Model Checking, checksPropertyType, safety properties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checksPropertyType Context triple: [Symbolic Model Checking, checksPropertyType, safety properties]
-
A.
hasPropertyType
Indicates that an entity possesses or is associated with a specific type or category of property.
-
B.
appliesToPropertyType
chosen
Indicates that something (such as a rule, constraint, or operation) is relevant to or valid for a specific type of property.
-
C.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
D.
typeOfPropertyManaged
Indicates the specific category or kind of property that an entity is responsible for managing.
-
E.
requiresProperty
Indicates that one entity depends on another entity possessing a specific property or attribute in order for a condition, action, or relationship to hold.
- F. None of above.
Provenance (3 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. |
Created at: March 30, 2026, 8:33 p.m.