Triple
T7696559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buhid |
E174384
|
entity |
| Predicate | hasVowelSign |
P16504
|
FINISHED |
| Object | inherent /a/ |
—
|
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: inherent /a/ | Statement: [Buhid, hasVowelSign, inherent /a/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVowelSign Context triple: [Buhid, hasVowelSign, inherent /a/]
-
A.
hasNumberOfVowelSigns
Indicates the count of vowel signs associated with or present in a given linguistic unit (such as a character, syllable, or word).
-
B.
hasVowelFeature
Indicates that an entity possesses a specific vowel-related phonological or articulatory feature.
-
C.
hasConsonantSigns
Indicates that one entity possesses or includes consonant sign characters as part of its representation or structure.
-
D.
hasDependentVowels
chosen
Indicates that a writing system or script uses vowel signs that are attached to or depend on consonant characters rather than standing alone as independent letters.
-
E.
hasVowelNotationSystem
Indicates that a writing or transcription system for a language includes a method for explicitly representing vowel sounds.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.