Triple
T35443795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sena language |
E1024425
|
entity |
| Predicate | hasRegionalVarieties |
P32680
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sena language, hasRegionalVarieties, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalVarieties Context triple: [Sena language, hasRegionalVarieties, yes]
-
A.
hasRegionalVariationsIn
chosen
Indicates that something exhibits different forms, versions, or characteristics depending on the geographic region.
-
B.
hasNonStandardizedVarieties
Indicates that an entity possesses forms or variants that are not governed by a uniform or officially established standard.
-
C.
hasLinguisticVariety
Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
-
D.
hasColloquialVariety
Indicates that one linguistic form, expression, or variety is an informal, colloquial counterpart or version of another.
-
E.
regionalVariantOf
Indicates that one entity is a version or form of another that is specific to a particular geographic region or locale.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.