Triple
T7898443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handlebars |
E183388
|
entity |
| Predicate | defaultEscaping |
P79653
|
FINISHED |
| Object | HTML-escaped output |
—
|
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: HTML-escaped output | Statement: [Handlebars, defaultEscaping, HTML-escaped output]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultEscaping Context triple: [Handlebars, defaultEscaping, HTML-escaped output]
-
A.
escapeBehavior
Indicates a relationship where an entity actively attempts to avoid, flee from, or get away from another entity, situation, or constraint.
-
B.
escapedBy
Indicates that an entity is freed or enabled to escape through the actions or intervention of another entity.
-
C.
afterEscape
Indicates that one event, state, or action occurs subsequent to or as a consequence of an escape.
-
D.
hasEscapeEnvironment
Indicates that an entity is associated with, or requires, a specific environment or context in which it can safely or successfully escape.
-
E.
requiresDoubleQuotedStrings
Indicates that the related element or operation must use double-quoted strings rather than other string delimiters.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a2ae5048190a6824d34b582c366 |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:01 p.m.