Triple
T24472108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matanvat |
E617127
|
entity |
| Predicate | hasAssociatedEthnolinguisticGroup |
P115409
|
FINISHED |
| Object | Nese speakers |
—
|
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: Nese speakers | Statement: [Matanvat, hasAssociatedEthnolinguisticGroup, Nese speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedEthnolinguisticGroup Context triple: [Matanvat, hasAssociatedEthnolinguisticGroup, Nese speakers]
-
A.
hasEthnicGroupType
Indicates that an entity is associated with, characterized by, or classified according to a particular type or category of ethnic group.
-
B.
hasEthnolinguisticPresence
chosen
Indicates that a particular ethnolinguistic group is present or represented within a specified place, context, or population.
-
C.
isUsedByEthnicGroup
Indicates that something (such as an object, practice, or resource) is utilized or employed by a particular ethnic group.
-
D.
mayBelongToEthnicGroup
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
-
E.
hasEthnicGroupDocumented
Indicates that an entity has a specific ethnic group recorded or documented as being associated with it.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29943e9cc81909f1742c778bf3587 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.