Triple
T22570052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Promi Lepcha |
E558053
|
entity |
| Predicate | hasSpokenBySubsetOf |
P114101
|
FINISHED |
| Object | Lepcha community |
—
|
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: Lepcha community | Statement: [Promi Lepcha, hasSpokenBySubsetOf, Lepcha community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpokenBySubsetOf Context triple: [Promi Lepcha, hasSpokenBySubsetOf, Lepcha community]
-
A.
isSubsetOfSpeakersOf
chosen
Indicates that the set of speakers of one language or variety is entirely contained within the set of speakers of another.
-
B.
hasSpokenAbout
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
-
C.
hasSpeakersAmong
Indicates that a group, event, or entity includes one or more speakers drawn from a specified set or category.
-
D.
hasSpokenFormOnly
Indicates that the entity exists or is recognized only in spoken form and has no corresponding written representation.
-
E.
isSpokenAlong
Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15fad35448190b51a3dd639ca8568 |
completed | April 29, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:52 p.m.