Triple

T12378934
Position Surface form Disambiguated ID Type / Status
Subject Machu Picchu station E295695 entity
Predicate hasSecondaryLanguageUsed P9103 FINISHED
Object English 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 | Statement: [Machu Picchu station, hasSecondaryLanguageUsed, English]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSecondaryLanguageUsed
Context triple: [Machu Picchu station, hasSecondaryLanguageUsed, English]
  • A. hasSecondaryLanguage chosen
    Indicates that an entity possesses or uses a secondary language in addition to its primary language.
  • B. hasSecondaryLanguageNearby
    Indicates that an entity has at least one secondary language present or used in its immediate vicinity or surrounding context.
  • C. hasSecondaryLanguageTradition
    Indicates that an entity possesses an additional, non-primary language tradition associated with it, such as in its use, documentation, or cultural context.
  • D. hasPrimaryLanguage1
    Indicates that an entity’s main or most commonly used language is the specified language.
  • E. laterSecondaryLanguageOfAdministration
    Indicates that one language served as a subsequent or later secondary language used for administrative purposes in relation to another language.
  • 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_69d6ad9e653c8190b1473c860ee53dae completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d93fb9eca48190aa6612ffc5ed0df2 completed April 10, 2026, 6:21 p.m.
PD Predicate disambiguation batch_69d93ed256788190b704cad171a4824e completed April 10, 2026, 6:17 p.m.
Created at: April 8, 2026, 9:54 p.m.