Triple
T27560037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GitHub Flavored Markdown |
E695745
|
entity |
| Predicate | supportsCodeFenceDelimiters |
P30848
|
FINISHED |
| Object | triple backticks ``` |
—
|
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: triple backticks ``` | Statement: [GitHub Flavored Markdown, supportsCodeFenceDelimiters, triple backticks ```]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCodeFenceDelimiters Context triple: [GitHub Flavored Markdown, supportsCodeFenceDelimiters, triple backticks ```]
-
A.
isFenced
Indicates that an entity is enclosed or surrounded by a fence or fencing structure.
-
B.
supportsLanguageMode
Indicates that one entity provides or is compatible with a particular language mode used or required by another entity.
-
C.
supportsDelimiterVariation
chosen
Indicates that one entity is capable of handling or accommodating different types or formats of delimiters used by another entity.
-
D.
supportsCommentsStyle
Indicates that one entity is capable of handling or displaying comments in a particular style or formatting convention.
-
E.
supportsEscapeSequences
Indicates that an entity can recognize and correctly process escape sequence characters within its input or content.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: April 27, 2026, 1:38 p.m.