Triple
T34895854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cubeo language |
E1006431
|
entity |
| Predicate | hasContactFeature |
P12914
|
FINISHED |
| Object | intensive multilingualism with other Vaupés languages |
—
|
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: intensive multilingualism with other Vaupés languages | Statement: [Cubeo language, hasContactFeature, intensive multilingualism with other Vaupés languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContactFeature Context triple: [Cubeo language, hasContactFeature, intensive multilingualism with other Vaupés languages]
-
A.
hasContactVariety
Indicates that one entity is associated with a specific type or variety of contact information or communication channel.
-
B.
hasContactState
Indicates that an entity is currently in a specific state or condition regarding its physical or communicative contact with another entity.
-
C.
hasContactType
chosen
Indicates the specific kind or category of contact relationship that exists between two entities.
-
D.
hasKontakion
Indicates that an entity is associated with or possesses a specific kontakion, i.e., a particular liturgical hymn or chant.
-
E.
hasContactMethod
Indicates that an entity has a specific way or channel through which it can be contacted.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.