Triple
T14439865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FreeMarker templates |
E358057
|
entity |
| Predicate | supportsDirectiveSyntax |
P30407
|
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, supportsDirectiveSyntax, <#...>]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDirectiveSyntax Context triple: [FreeMarker templates, supportsDirectiveSyntax, <#...>]
-
A.
supportsDirective
Indicates that one entity upholds, endorses, or helps implement a directive issued by another entity.
-
B.
hasDirective
Indicates that one entity issues, contains, or is governed by a specific directive or instruction associated with another entity.
-
C.
usesDirective
chosen
Indicates that one entity applies, references, or relies on a specific directive issued or defined by another entity.
-
D.
supportsInstruction
Indicates that one entity provides assistance, resources, or functionality that enables or facilitates the instruction or teaching activities of another entity.
-
E.
supportsStyleDefinition
Indicates that one entity is capable of handling, recognizing, or working with a particular style definition associated with 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.