Triple
T29630038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hixkaryana and Linguistic Typology |
E755546
|
entity |
| Predicate | aboutLanguageFamily |
P150821
|
FINISHED |
| Object | Cariban languages |
—
|
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: Cariban languages | Statement: [Hixkaryana and Linguistic Typology, aboutLanguageFamily, Cariban languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aboutLanguageFamily Context triple: [Hixkaryana and Linguistic Typology, aboutLanguageFamily, Cariban languages]
-
A.
coversLanguageFamily
chosen
Indicates that one entity includes or encompasses a particular language family within its scope or subject matter.
-
B.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
C.
languageFamilyBranchOf
Indicates that one language family branch is a sub-group or subdivision within a larger language family.
-
D.
languageOfFamily
Indicates the language or languages commonly used or associated with a particular family.
-
E.
studiesLanguageFamily
Indicates that an entity engages in the academic or systematic study of a particular language family.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66e64ac588190a91481917a6e91da |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:40 p.m.