Triple

T35183280
Position Surface form Disambiguated ID Type / Status
Subject Loniu Passage E1015911 entity
Predicate hasLanguageInVicinity P91957 FINISHED
Object Loniu language NE NERFINISHED

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: Loniu language | Statement: [Loniu Passage, hasLanguageInVicinity, Loniu language]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLanguageInVicinity
Context triple: [Loniu Passage, hasLanguageInVicinity, Loniu language]
  • A. hasPrimaryLanguageNearby chosen
    Indicates that an entity is associated with a primary language that is predominantly used or present in its immediate geographic or contextual vicinity.
  • B. hasStandardLanguageNearby
    Indicates that a standard or commonly used language is present in close proximity to the referenced entity.
  • C. hasSecondaryLanguageNearby
    Indicates that an entity has at least one secondary language present or used in its immediate vicinity or surrounding context.
  • D. hasLanguageOfSurroundingCountries
    Indicates that an entity uses or includes the languages commonly spoken in the countries that geographically surround it.
  • E. hasNeighboringLanguages
    Indicates that two languages are geographically or regionally adjacent to each other in their areas of use.
  • 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_69f76ddd815c8190b822eea06630f9fb completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ff7ae5d088819089aa3b6360b6b749 completed May 9, 2026, 6:20 p.m.
PD Predicate disambiguation batch_69ff7a4df6488190bf60d675b36b1d6d completed May 9, 2026, 6:17 p.m.
Created at: May 3, 2026, 4:02 p.m.