Triple

T18179127
Position Surface form Disambiguated ID Type / Status
Subject Appendix English Language E435236 entity
Predicate languageRequirementType P103498 FINISHED
Object English language 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: English language | Statement: [Appendix English Language, languageRequirementType, English language]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: languageRequirementType
Context triple: [Appendix English Language, languageRequirementType, English language]
  • A. qualificationRequirementType
    Indicates the kind or category of qualification that is required in a given context or for a specific role, task, or opportunity.
  • B. requiredLanguage chosen
    Indicates that a specific language is necessary or must be used for a given entity, action, or interaction.
  • C. evaluationRequirement
    Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
  • D. clientRequirement
    Indicates that one party specifies a need, condition, or expectation that must be met by another party (typically a service provider or system).
  • E. hasProfessionalRequirement
    Indicates that one entity imposes or specifies a professional qualification, credential, or condition that must be met 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_69d8b90c7ec081909b4694ccecb449c6 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dff9aad081909cc7eed2b64828f2 completed April 19, 2026, 2 p.m.
PD Predicate disambiguation batch_69e4331baeb88190b21f50a98c36c78e completed April 19, 2026, 1:42 a.m.
Created at: April 10, 2026, 10:31 a.m.