Triple

T4832124
Position Surface form Disambiguated ID Type / Status
Subject MediaWiki E107967 entity
Predicate supportsPageRedirects P203 FINISHED
Object redirect pages 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: redirect pages | Statement: [MediaWiki, supportsPageRedirects, redirect pages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsPageRedirects
Context triple: [MediaWiki, supportsPageRedirects, redirect pages]
  • A. supportsLinks
    Indicates that one entity provides backing, endorsement, or assistance to another entity through connections or references (such as hyperlinks or relational links).
  • B. supportsRouting
    Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
  • C. supportsSearchEngineFriendlyURLs
    Indicates that an entity provides or is compatible with URLs structured to be easily readable and indexable by search engines.
  • D. supportsFeature chosen
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • E. supportedIn
    Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by 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_69bd43fac8188190803f0327190621e4 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ff981fc819080d4466c6fe06cf3 completed March 20, 2026, 4:04 p.m.
PD Predicate disambiguation batch_69bd6c21c7f08190846049d31fdfa144 completed March 20, 2026, 3:47 p.m.
Created at: March 20, 2026, 1:24 p.m.