Triple

T1851765
Position Surface form Disambiguated ID Type / Status
Subject Tsakonian E41609 entity
Predicate consideredBySomeAs P21336 FINISHED
Object separate 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: separate language | Statement: [Tsakonian, consideredBySomeAs, separate language]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consideredBySomeAs
Context triple: [Tsakonian, consideredBySomeAs, separate language]
  • A. considered
    Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
  • B. couldConsider
    Indicates that one entity has the potential or option to take another entity into account when making a decision, judgment, or evaluation.
  • C. considersItself
    Indicates that an entity regards or perceives itself in a particular way, role, or state.
  • D. isSometimesClassifiedAs
    Indicates that an entity is occasionally, but not consistently or universally, categorized under a particular type or class.
  • E. viewedBySomeAs chosen
    Indicates that at least one observer or group perceives or interprets an entity in a particular way or role.
  • 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_69a8864a83848190a4ec02721306c511 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb32d35508190bf1c487dffbecaf0 completed March 7, 2026, 5:10 a.m.
PD Predicate disambiguation batch_69abafdca6d8819083c66f3a29fd9fd1 completed March 7, 2026, 4:55 a.m.
Created at: March 4, 2026, 7:33 p.m.