Triple
T19625700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purusha |
E471126
|
entity |
| Predicate | thighsGiveRiseTo |
P136751
|
FINISHED |
| Object | Vaishya varna |
—
|
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: Vaishya varna | Statement: [Purusha, thighsGiveRiseTo, Vaishya varna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thighsGiveRiseTo Context triple: [Purusha, thighsGiveRiseTo, Vaishya varna]
-
A.
legs
Indicates that an entity possesses legs, specifying the presence or number of leg-like appendages associated with it.
-
B.
torse
Indicates a heraldic depiction where a twisted roll of fabric (the torse) encircles the top of a helmet, typically serving as the base for a crest.
-
C.
isProminentPartOf
Indicates that something forms a major, highly noticeable, or significant component of a larger whole.
-
D.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an entity.
-
E.
hasThoracicLegs
Indicates that an entity possesses legs located in the thoracic (mid-body) region.
- F. None of above. chosen
Provenance (4 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e9ff208190afb33c910ed2147b |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:44 p.m.