Triple
T95849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pascal |
E1927
|
entity |
| Predicate | controlStructure |
P4116
|
FINISHED |
| Object | if-then-else |
—
|
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: if-then-else | Statement: [Pascal, controlStructure, if-then-else]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlStructure Context triple: [Pascal, controlStructure, if-then-else]
-
A.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
B.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
C.
decisionLanguage
Indicates that a decision, statement, or choice is expressed or recorded in a particular natural language.
-
D.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
E.
branchChecked
Indicates that a specific branch (such as in version control or a decision tree) has been examined or verified.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a250cb400c8190b56343bbe19b48c7 |
completed | Feb. 28, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69a24ebd19c48190bab291fea0ecc0c2 |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a250ca7eec8190b31f7e61f5e3ee1f |
completed | Feb. 28, 2026, 2:19 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.