Triple
T21976049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khas people |
E542705
|
entity |
| Predicate | identityChange |
P96087
|
FINISHED |
| Object | many Khas adopted surnames like Bahun and Chhetri |
—
|
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: many Khas adopted surnames like Bahun and Chhetri | Statement: [Khas people, identityChange, many Khas adopted surnames like Bahun and Chhetri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identityChange Context triple: [Khas people, identityChange, many Khas adopted surnames like Bahun and Chhetri]
-
A.
nameChangeAssociatedWith
Indicates that a change in one entity’s name is linked or correlated with a change or event involving another entity.
-
B.
athleticIdentityChange
Indicates a change in an entity’s status, role, or self-concept specifically related to its athletic or sports-related identity.
-
C.
changedSurnameFrom
Indicates that an entity has adopted a new surname that was previously a different, specified surname.
-
D.
adoptedIdentity
chosen
Indicates that one entity has taken on or assumed the identity, role, or persona of another entity, either formally or informally.
-
E.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f124886418819091daed0988432350 |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:03 p.m.