Triple

T2081707
Position Surface form Disambiguated ID Type / Status
Subject Austronesian alignment E45257 entity
Predicate resembles P35666 FINISHED
Object Philippine-type voice system 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: Philippine-type voice system | Statement: [Austronesian alignment, resembles, Philippine-type voice system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: resembles
Context triple: [Austronesian alignment, resembles, Philippine-type voice system]
  • A. emulates
    Indicates that one entity imitates or reproduces the behavior, function, or characteristics of another.
  • B. materiallySimilarTo
    Indicates that two entities share substantially the same physical or material characteristics, composition, or properties, though they may not be exactly identical.
  • C. synonym
    Indicates that two terms have the same or nearly the same meaning in a given context.
  • D. reversed
    Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
  • E. reflects
    Indicates that one entity (often a surface, medium, or representation) throws back, mirrors, or otherwise shows an image, property, or state of another entity.
  • F. None of above. chosen

Provenance (4 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_69a8891869c88190a02643e3bb746f59 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abba35c2588190933dba882f52dd17 completed March 7, 2026, 5:40 a.m.
PD Predicate disambiguation batch_69abb7b298a48190b4bdf7c9800b058d completed March 7, 2026, 5:29 a.m.
PDg Predicate description generation batch_69abb94ec400819097596732aabed854 completed March 7, 2026, 5:36 a.m.
Created at: March 4, 2026, 7:41 p.m.