Triple
T33342367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teke-Eboo languages |
E853704
|
entity |
| Predicate | havePhonologicalFeatures |
P48839
|
FINISHED |
| Object | tone |
—
|
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: tone | Statement: [Teke-Eboo languages, havePhonologicalFeatures, tone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: havePhonologicalFeatures Context triple: [Teke-Eboo languages, havePhonologicalFeatures, tone]
-
A.
hasPhonologicalParameters
chosen
Indicates that an entity is associated with specific phonological features or parameters that characterize its sound structure.
-
B.
hasPhonologicalDescription
Indicates that an entity is associated with a specific representation or description of its sound structure or phonological form.
-
C.
hasPhonologicalType
Indicates that one entity is characterized by or classified as having a particular phonological type (e.g., in terms of sound structure or phonological category).
-
D.
hasPhoneme
Indicates that a linguistic unit (such as a word or morpheme) contains or includes a particular phoneme as part of 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.