Triple
T23955916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chhetri |
E603786
|
entity |
| Predicate | socialClassificationInNepal |
P100400
|
FINISHED |
| Object | forward caste |
—
|
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: forward caste | Statement: [Chhetri, socialClassificationInNepal, forward caste]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialClassificationInNepal Context triple: [Chhetri, socialClassificationInNepal, forward caste]
-
A.
roleInNepal
Indicates that an entity holds or has held a specific role, position, or function within the context of Nepal.
-
B.
entryPointFromNepal
Indicates that something serves as an entry point or access route originating from Nepal.
-
C.
regionClassification
Indicates how a given area or location is categorized into a specific region based on defined criteria or boundaries.
-
D.
classificationAccordingTo
chosen
Indicates that an entity is assigned a particular class, type, or category as defined or determined by a specified source, standard, or authority.
-
E.
bordersAdministrativeRegionOfNepal
Indicates that one administrative region of Nepal shares a common boundary with another administrative region of Nepal.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d6d7688190bedf55dda8e72b2b |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.