Triple

T7523545
Position Surface form Disambiguated ID Type / Status
Subject Mon people E177833 entity
Predicate historicalLanguageRole P29914 FINISHED
Object prestige language in early mainland Southeast Asia 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: prestige language in early mainland Southeast Asia | Statement: [Mon people, historicalLanguageRole, prestige language in early mainland Southeast Asia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalLanguageRole
Context triple: [Mon people, historicalLanguageRole, prestige language in early mainland Southeast Asia]
  • A. historicalLanguage
    Indicates that one language is a historical or earlier form/ancestor of another language.
  • B. languageOfHistoricalRecord
    Indicates the language in which a given historical record is written or recorded.
  • C. historicallySpoke
    Indicates that an entity used a particular language as a spoken language during some period in the past.
  • D. historicalLanguageStage
    Indicates that one language variety represents an earlier historical stage or developmental phase of another language.
  • E. hasHistoricalRoleAs chosen
    Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
  • 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_69c69f29bf3081909a146aec7755f185 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f7c4f32081908b5162f4551adb6d completed March 27, 2026, 9:33 p.m.
PD Predicate disambiguation batch_69c6f4d6bb808190bdd04499fd3bceb6 completed March 27, 2026, 9:21 p.m.
Created at: March 27, 2026, 3:46 p.m.