Triple

T5370796
Position Surface form Disambiguated ID Type / Status
Subject Amalias Avenue E108843 entity
Predicate officialNameLanguageCode P26955 FINISHED
Object el 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: el | Statement: [Amalias Avenue, officialNameLanguageCode, el]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: officialNameLanguageCode
Context triple: [Amalias Avenue, officialNameLanguageCode, el]
  • A. hasLanguageOfOfficialName chosen
    Indicates that an entity’s official name is expressed in a specified language.
  • B. officialLanguage
    Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
  • C. nationalLanguageStandardizedIn
    Indicates that a national language has been formally standardized or codified within a particular country or jurisdiction.
  • D. standardLanguageOf
    Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
  • E. shareOfficialLanguage
    Indicates that two entities have at least one official language in common.
  • 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_69bd440c77948190aad2a5f39b7b80f5 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd88801b188190b9ac35ed89167fa3 completed March 20, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69bd846172788190969f24bc7503c05e completed March 20, 2026, 5:31 p.m.
Created at: March 20, 2026, 2:02 p.m.