Triple
T35848973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushki |
E1036293
|
entity |
| Predicate | ethnicIdentification |
P156628
|
FINISHED |
| Object | uncertain |
—
|
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: uncertain | Statement: [Mushki, ethnicIdentification, uncertain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicIdentification Context triple: [Mushki, ethnicIdentification, uncertain]
-
A.
ethnicIdentityOf
chosen
Indicates that one entity is the ethnic identity or affiliation possessed by another entity.
-
B.
racialIdentity
Indicates the relationship between an entity and the racial group or classification with which it is identified or categorized.
-
C.
ethnoreligiousIdentity
Indicates a relationship where an entity is characterized by a combined ethnic and religious group identity.
-
D.
ethnicGroupClassifiedAs
Indicates that an ethnic group is categorized or designated as belonging to a particular classification or type of ethnic grouping.
-
E.
ethnicComponents
Indicates that an entity is composed of, associated with, or characterized by one or more specified ethnic groups or ethnic origins.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4:06 p.m.