Triple
T38079183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virūḷhaka |
E950803
|
entity |
| Predicate | directionalGroup |
P197312
|
FINISHED |
| Object | Lokapālas |
—
|
NE NERFINISHED |
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: Lokapālas | Statement: [Virūḷhaka, directionalGroup, Lokapālas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionalGroup Context triple: [Virūḷhaka, directionalGroup, Lokapālas]
-
A.
directionalConfiguration
Indicates a specific spatial or directional arrangement that one entity has relative to another.
-
B.
directionalDesignation
Indicates a relationship where one entity is assigned or labeled with a specific directional orientation relative to another entity or reference frame.
-
C.
directionalRole
Indicates a role or function defined in terms of a direction or orientation relative to another entity or reference frame.
-
D.
isDirectional
Indicates that something has an inherent or assigned direction, specifying orientation or flow from one point or entity to another.
-
E.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
| PDg | Predicate description generation | batch_69fe86c98d688190a99d5dcb14e2dc95 |
completed | May 9, 2026, 12:58 a.m. |
Created at: May 3, 2026, 4:21 p.m.