Triple
T14439864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FreeMarker templates |
E358057
|
entity |
| Predicate | supportsPlaceholderSyntax |
P114282
|
FINISHED |
| Object | ${...} |
—
|
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: ${...} | Statement: [FreeMarker templates, supportsPlaceholderSyntax, ${...}]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPlaceholderSyntax
Context triple: [FreeMarker templates, supportsPlaceholderSyntax, ${...}]
-
A.
supportsPositionalParameters
Indicates that one entity allows or enables the use of positional parameters when invoking an operation or function.
-
B.
supportsTemplateEnginesViaExtensions
Indicates that something provides compatibility with template engines through the use of extensions.
-
C.
supportsDelimiterVariation
Indicates that one entity is capable of handling or accommodating different types or formats of delimiters used by another entity.
-
D.
supportsTag
Indicates that one entity is capable of recognizing, handling, or being associated with a specified tag.
-
E.
supportsPartialMatch
Indicates that the relationship or operation allows matching based on a subset or portion of the target criteria rather than requiring a complete or exact match.
- 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_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. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:18 a.m.