Triple
T860881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arjuna Vishada Yoga |
E18595
|
entity |
| Predicate | hasOrderInWork |
P1109
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Arjuna Vishada Yoga, hasOrderInWork, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderInWork Context triple: [Arjuna Vishada Yoga, hasOrderInWork, 1]
-
A.
hasOrder
chosen
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
B.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
C.
orderInOffice
Indicates that one entity holds a specific sequential position or rank within a defined term or period of holding an office or official role.
-
D.
hasStandingOrders
Indicates that an entity has pre-authorized, recurring instructions or arrangements in place to be executed automatically under specified conditions.
-
E.
hasLayOrder
Indicates that one entity has issued, received, or is subject to a formal lay order associated with another entity.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac52536c8190ab198232e9ec4bd6 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.