Triple

T23505367
Position Surface form Disambiguated ID Type / Status
Subject Chintang language E572265 entity
Predicate hasConstituentOrder P1109 FINISHED
Object SOV 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: SOV | Statement: [Chintang language, hasConstituentOrder, SOV]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasConstituentOrder
Context triple: [Chintang language, hasConstituentOrder, SOV]
  • A. hasOrderStructure
    Indicates that there is a defined ordering relation imposed on the elements of a set or collection, specifying how they are arranged or compared in terms of order.
  • B. hasOrder chosen
    Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
  • C. hasElementOrdersUpTo
    Indicates that one entity includes or supports elements whose orders (e.g., magnitudes, degrees, or hierarchical levels) do not exceed a specified upper limit defined by the other entity.
  • D. hasElementOrder
    Indicates that one entity is ordered or ranked relative to another within a sequence or hierarchy.
  • E. isOrderOf
    Indicates that one entity specifies the sequence, arrangement, or ranking in which elements of another entity are organized or occur.
  • 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_69e245b5e4208190bac8a6509867e394 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a8ff97c88190a67f787e1674619e completed April 29, 2026, 6:45 a.m.
PD Predicate disambiguation batch_69f0621165c08190a0b27b1319733959 completed April 28, 2026, 7:30 a.m.
Created at: April 17, 2026, 6:07 p.m.