Triple
T33778227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bongomek |
E865579
|
entity |
| Predicate | sharesPhonologicalFeaturesWith |
P8038
|
FINISHED |
| Object | Sabaot 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: Sabaot language | Statement: [Bongomek, sharesPhonologicalFeaturesWith, Sabaot language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesPhonologicalFeaturesWith Context triple: [Bongomek, sharesPhonologicalFeaturesWith, Sabaot language]
-
A.
hasPhonologicalSimilarityTo
chosen
Indicates that two linguistic elements share similar sound patterns or phonological features.
-
B.
hasPhonologicalBasisFor
Indicates that one entity serves as the phonological source, motivation, or foundation for another entity.
-
C.
hasDialectalFeaturesSharedWith
Indicates that two language varieties share specific dialectal features or characteristics in common.
-
D.
hasPhonologicalParameters
Indicates that an entity is associated with specific phonological features or parameters that characterize its sound structure.
-
E.
hasOwnPhonology
Indicates that an entity possesses its own distinct phonological system or set of sound patterns, separate from those of other entities.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
Created at: May 1, 2026, 1:45 a.m.