Triple

T11673839
Position Surface form Disambiguated ID Type / Status
Subject Shakya E277441 entity
Predicate relatedClanNameEtymology P64092 FINISHED
Object derived from Sanskrit "śakya" meaning "capable" or "able" 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: derived from Sanskrit "śakya" meaning "capable" or "able" | Statement: [Shakya, relatedClanNameEtymology, derived from Sanskrit "śakya" meaning "capable" or "able"]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relatedClanNameEtymology
Context triple: [Shakya, relatedClanNameEtymology, derived from Sanskrit "śakya" meaning "capable" or "able"]
  • A. clanNameOrigin
    Indicates the source or basis from which a clan’s name is derived.
  • B. possibleNameEtymology chosen
    Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
  • C. nameEtymologyFor
    Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
  • D. clanNameVariant
    Indicates that one clan name is an alternative or variant form of another clan name.
  • E. etymologyRelatesTo
    Indicates a relationship where one term’s origin, history, or derivation is connected to another linguistic form, word, or source.
  • 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_69d6aafd0a448190b44da30af8c6c519 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a443b6848190a1eb6825fbc49d08 completed April 10, 2026, 7:18 a.m.
PD Predicate disambiguation batch_69d88a77e6e88190b7519100bde76575 completed April 10, 2026, 5:28 a.m.
Created at: April 8, 2026, 9:40 p.m.