Triple
T32133793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khas Arya |
E820717
|
entity |
| Predicate | associatedCasteStatus |
P16727
|
FINISHED |
| Object | high 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: high caste | Statement: [Khas Arya, associatedCasteStatus, high caste]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCasteStatus Context triple: [Khas Arya, associatedCasteStatus, high caste]
-
A.
associatedWithCaste
Indicates a relationship where an entity is linked or connected to a particular caste, typically by social, cultural, or hereditary association.
-
B.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
C.
hasCaste
chosen
Indicates that an entity belongs to or is associated with a particular caste within a social or hierarchical system.
-
D.
associatedPeopleStatus
Indicates the role, condition, or standing of people who are connected or linked to a given entity or event.
-
E.
associatedWithCandidateStatus
Indicates that there is a relationship linking an entity to a particular status or stage in a candidate-related process.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:30 a.m.