Triple

T27560035
Position Surface form Disambiguated ID Type / Status
Subject GitHub Flavored Markdown E695745 entity
Predicate supportsTableSyntax P80839 FINISHED
Object pipe-separated rows 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: pipe-separated rows | Statement: [GitHub Flavored Markdown, supportsTableSyntax, pipe-separated rows]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsTableSyntax
Context triple: [GitHub Flavored Markdown, supportsTableSyntax, pipe-separated rows]
  • A. supportsExpressionType
    Indicates that one entity is capable of handling, processing, or being compatible with a specified type of expression.
  • B. supportsPlaceholderSyntax
    Indicates that one entity provides or is compatible with a placeholder-based syntax used for parameterization or substitution in another entity.
  • C. supportsPartitionTable
    Indicates that one entity provides the capability to create, manage, or operate on partitioned tables for another entity.
  • D. supportsRowFormat chosen
    Indicates that one entity provides compatibility with or can correctly handle the specified row format of another entity.
  • E. theorySupports
    Indicates that one theory provides justification, evidence, or logical backing for another claim, theory, or proposition.
  • 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_69fef112398081909237c3872345968b completed May 9, 2026, 8:32 a.m.
PD Predicate disambiguation batch_69feefb14ec08190ab401987d8c84a23 completed May 9, 2026, 8:26 a.m.
Created at: April 27, 2026, 1:38 p.m.