Triple
T4738607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purusha Sukta |
E105183
|
entity |
| Predicate | portraysPurushaAs |
P58494
|
FINISHED |
| Object | thousand-headed being |
—
|
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: thousand-headed being | Statement: [Purusha Sukta, portraysPurushaAs, thousand-headed being]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysPurushaAs Context triple: [Purusha Sukta, portraysPurushaAs, thousand-headed being]
-
A.
portraysActorAs
Indicates that one entity depicts or represents an actor in a particular role, character, or manner.
-
B.
portrayedAsFrom
Indicates that one entity is depicted or represented as originating from, or belonging to, the place or source specified by another entity.
-
C.
portraysFictionalEntity
Indicates that one entity depicts, represents, or plays the role of a fictional character or figure.
-
D.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
E.
depictedSubject
Indicates that one entity visually represents or portrays another entity as its subject in an image or depiction.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6485d690819098dc4a974516da6b |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd637e19e081909e415544106c7835 |
completed | March 20, 2026, 3:10 p.m. |
Created at: March 20, 2026, 1:19 p.m.