Triple
T4783288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulupi |
E106415
|
entity |
| Predicate | laterExplained |
P59295
|
FINISHED |
| Object | her actions to Arjuna as intended for his welfare |
—
|
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: her actions to Arjuna as intended for his welfare | Statement: [Ulupi, laterExplained, her actions to Arjuna as intended for his welfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterExplained Context triple: [Ulupi, laterExplained, her actions to Arjuna as intended for his welfare]
-
A.
laterDevelopments
Indicates that subsequent events, changes, or outcomes occurred following an earlier situation or state.
-
B.
laterFeature
Indicates that one feature, event, or element occurs or is introduced after another in time.
-
C.
laterDescribedAs
Indicates that an entity is referred to or characterized by a particular description or label at a later time.
-
D.
laterComplementedBy
Indicates that an earlier entity is subsequently supplemented, enhanced, or completed by a later entity.
-
E.
laterActivity
Indicates that one activity occurs after another in time, establishing a temporal ordering between them.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6922407481908565ed0b1dac2b30 |
completed | March 20, 2026, 3:34 p.m. |
Created at: March 20, 2026, 1:22 p.m.