Triple
T17675789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERB |
E440638
|
entity |
| Predicate | supportsControlFlow |
P3686
|
FINISHED |
| Object | if statements in templates |
—
|
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 statements in templates | Statement: [ERB, supportsControlFlow, if statements in templates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsControlFlow Context triple: [ERB, supportsControlFlow, if statements in templates]
-
A.
controlStructure
Indicates a relationship where one entity governs, regulates, or directs the behavior, operation, or flow of another entity or process.
-
B.
continuesToControl
Indicates that one entity maintains ongoing authority, influence, or command over another entity or resource over time.
-
C.
flowControl
chosen
Indicates a relationship where one entity regulates, directs, or manages the rate or sequence of another entity’s operations or movement.
-
D.
supportsJobControlLanguage
Indicates that one entity provides compatibility with or the ability to execute and manage operations defined in a job control language for another entity.
-
E.
controlledFor
Indicates that the influence or effect of a specified factor has been accounted for or neutralized when assessing the relationship between other variables or entities.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6cca54819094ea0bed1517724e |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10 a.m.