Triple
T14439867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FreeMarker templates |
E358057
|
entity |
| Predicate | supportsControlStructure |
P4116
|
FINISHED |
| Object | if |
—
|
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 | Statement: [FreeMarker templates, supportsControlStructure, if]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsControlStructure Context triple: [FreeMarker templates, supportsControlStructure, if]
-
A.
controlStructure
chosen
Indicates a relationship where one entity governs, regulates, or directs the behavior, operation, or flow of another entity or process.
-
B.
supportsStructure
Indicates that one entity bears or provides physical support to another entity, helping to hold it up or maintain its structural stability.
-
C.
structuralControlOn
Indicates that one entity exerts structural influence or constraint over another, affecting its form, configuration, or organization.
-
D.
supportsBlocksClosures
Indicates that one entity provides compatibility or functionality for another entity’s use of blocks or closures.
-
E.
supportsBlockBasedCoding
Indicates that an entity provides or enables functionality for creating programs using a block-based visual coding interface.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914c1398819090fa2a74d257ba3e |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.