Triple
T18791308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dijkstra weakest precondition calculus |
E459519
|
entity |
| Predicate | hasRuleFor |
P133032
|
FINISHED |
| Object | assignment statement |
—
|
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: assignment statement | Statement: [Dijkstra weakest precondition calculus, hasRuleFor, assignment statement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuleFor Context triple: [Dijkstra weakest precondition calculus, hasRuleFor, assignment statement]
-
A.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
B.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
C.
hasRuleName
Indicates that an entity is associated with a specific rule identified by a particular name.
-
D.
hasNumberOfRules
Indicates the specific count of rules associated with or applicable to an entity.
-
E.
hasInheritanceRule
Indicates that a specific rule or policy governs how rights, properties, or attributes are passed from one entity to another.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5978665388190aaefed0ec30a1ff3 |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:53 a.m.