Triple
T19812293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ocean of Milk |
E475975
|
entity |
| Predicate | purposeOfChurning |
P79
|
FINISHED |
| Object | to obtain amrita |
—
|
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: to obtain amrita | Statement: [Ocean of Milk, purposeOfChurning, to obtain amrita]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfChurning Context triple: [Ocean of Milk, purposeOfChurning, to obtain amrita]
-
A.
purposeOfLiquidation
Indicates that a liquidation event is carried out for a specific intended purpose or objective.
-
B.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
C.
operationalPurpose
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
-
D.
findsPurposeThrough
Indicates that one entity derives its sense of purpose, meaning, or fulfillment through its relationship with or actions involving another entity.
-
E.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6542c9c5c81908772e88caa067e63 |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.