Triple

T1096426
Position Surface form Disambiguated ID Type / Status
Subject XML Namespaces E24280 entity
Predicate defaultNamespaceDoesNotApplyTo P7029 FINISHED
Object unprefixed attribute names 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: unprefixed attribute names | Statement: [XML Namespaces, defaultNamespaceDoesNotApplyTo, unprefixed attribute names]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defaultNamespaceDoesNotApplyTo
Context triple: [XML Namespaces, defaultNamespaceDoesNotApplyTo, unprefixed attribute names]
  • A. doesNotGenerallyApplyTo chosen
    Indicates that a rule, property, or condition is typically not relevant or applicable to the referenced entity or situation in most cases.
  • B. usesNamingSystem
    Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
  • C. appliesTo
    Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
  • D. appliesToFeature
    Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
  • E. doesNotSpecify
    Indicates that the subject intentionally leaves some information, detail, or attribute undefined or unspecified with respect to the object.
  • 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_69a4940542308190ac2a0b1f730b7cfc completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b99ffb3481908cd168b6c58e1c6d completed March 1, 2026, 10:11 p.m.
PD Predicate disambiguation batch_69a4b7448c148190a3c9a4158ebd05b4 completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:42 p.m.