Triple
T19111867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlusCal |
E467808
|
entity |
| Predicate | hasControlConstruct |
P69545
|
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: [PlusCal, hasControlConstruct, if-then-else]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlConstruct Context triple: [PlusCal, hasControlConstruct, if-then-else]
-
A.
hasControlElement
Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
-
B.
hasControlBranch
chosen
Indicates that one entity possesses a controlling or decision-making branch or subdivision within another entity or system.
-
C.
hasControlFields
Indicates that one entity possesses or defines control-related parameters, settings, or fields that govern the behavior or configuration of another entity or process.
-
D.
hasModuleConstruct
Indicates that an entity includes, defines, or is composed of a specific module as one of its structural or functional components.
-
E.
hasConstructor
Indicates that an entity defines or is associated with a specific constructor used to create or initialize instances of it.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e394969c81909d09b2300ea0e041 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:04 p.m.