Triple
T14439839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velocity templates |
E358056
|
entity |
| Predicate | usesPlaceholderSyntax |
P51567
|
FINISHED |
| Object | $variable |
—
|
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: $variable | Statement: [Velocity templates, usesPlaceholderSyntax, $variable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPlaceholderSyntax Context triple: [Velocity templates, usesPlaceholderSyntax, $variable]
-
A.
usesBracket
Indicates that one entity employs or incorporates a bracket as a structural or functional component in relation to another entity.
-
B.
usesExpressionSystem
Indicates that one entity employs or relies on a particular expression system (e.g., a biological, genetic, or computational framework) to produce, express, or manipulate another entity.
-
C.
usedAsPrefixIn
Indicates that one element functions as a leading prefix component in the formation or representation of another element.
-
D.
usedInExpression
chosen
Indicates that one entity (typically a term, symbol, or construct) is employed as a component within another entity that represents an expression.
-
E.
usesAliasTo
Indicates that one entity employs an alternative name or identifier to refer to or represent another entity.
- 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.