Triple

T416946
Position Surface form Disambiguated ID Type / Status
Subject Thomas Young E8012 entity
Predicate languageSkills P741 FINISHED
Object knew multiple classical and modern languages 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: knew multiple classical and modern languages | Statement: [Thomas Young, languageSkills, knew multiple classical and modern languages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: languageSkills
Context triple: [Thomas Young, languageSkills, knew multiple classical and modern languages]
  • A. languagesSpoken chosen
    Indicates that an entity is able to communicate using one or more specified languages.
  • B. languageProvision
    Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
  • C. languageOfExpression
    Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
  • D. isWidelySpokenIn
    Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
  • E. languageOfWorkOrName
    Indicates the language in which a work is created or a name is expressed.
  • 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_69a2e7f1d1bc81909cf2dc9754a3c334 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eebde1d881908fb212bfba9d7c67 completed Feb. 28, 2026, 1:33 p.m.
PD Predicate disambiguation batch_69a2edd1ca148190a66bd8c5aad867d5 completed Feb. 28, 2026, 1:29 p.m.
Created at: Feb. 28, 2026, 1:11 p.m.