Triple
T19625698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purusha |
E471126
|
entity |
| Predicate | headGivesRiseTo |
P136749
|
FINISHED |
| Object | Brahmin 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: Brahmin varna | Statement: [Purusha, headGivesRiseTo, Brahmin varna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headGivesRiseTo Context triple: [Purusha, headGivesRiseTo, Brahmin varna]
-
A.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
B.
heads
Indicates that one entity leads, directs, or is in charge of another entity, such as an organization, group, or initiative.
-
C.
headsToward
Indicates movement or orientation in the direction of a particular target or destination.
-
D.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
-
E.
headColor
Indicates the color attribute specifically associated with the head of an entity.
- 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.