Triple
T22951382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Botatwe languages |
E570026
|
entity |
| Predicate | haveSharedMorphologicalFeatures |
P31789
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Botatwe languages, haveSharedMorphologicalFeatures, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveSharedMorphologicalFeatures Context triple: [Botatwe languages, haveSharedMorphologicalFeatures, true]
-
A.
hasDialectalFeaturesSharedWith
Indicates that two language varieties share specific dialectal features or characteristics in common.
-
B.
hasMorphologyDistinctFrom
Indicates that the morphology (form or structure) of one entity is different from that of another entity.
-
C.
hasMorphologicalMix
Indicates that an entity exhibits a combination of different morphological types or structures within a single form or system.
-
D.
relatedMorphologicalFeature
chosen
Indicates that one entity is connected to another through a shared or corresponding morphological feature or structure.
-
E.
hasLinguisticFeature
Indicates that an entity possesses a particular linguistic property, trait, or characteristic.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181a285448190a718734fe933d51a |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:46 p.m.