Triple
T17675783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERB |
E440638
|
entity |
| Predicate | supportsEscaping |
P79653
|
FINISHED |
| Object | HTML escaping via ERB::Util |
—
|
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 escaping via ERB::Util | Statement: [ERB, supportsEscaping, HTML escaping via ERB::Util]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsEscaping Context triple: [ERB, supportsEscaping, HTML escaping via ERB::Util]
-
A.
supportsEscapeSequences
Indicates that an entity can recognize and correctly process escape sequence characters within its input or content.
-
B.
defaultEscaping
chosen
Indicates that a value, expression, or output is automatically transformed (escaped) into a safe representation by default to prevent unintended interpretation or execution.
-
C.
escapesWith
Indicates that one entity flees or breaks free from a situation, place, or constraint together with another entity as a companion or accomplice.
-
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.
escapedBy
Indicates that an entity is freed or enabled to escape through the actions or intervention of 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6cca54819094ea0bed1517724e |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10 a.m.