Triple
T25581215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MP 59 |
E641244
|
entity |
| Predicate | withdrawalStatus |
P158869
|
FINISHED |
| Object | being phased out |
—
|
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: being phased out | Statement: [MP 59, withdrawalStatus, being phased out]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withdrawalStatus Context triple: [MP 59, withdrawalStatus, being phased out]
-
A.
withdrawalsStatusAtActivation
Indicates the status or condition of withdrawals at the moment an account, contract, or system is activated.
-
B.
hasWithdrawal
Indicates that an entity performs, experiences, or is associated with a withdrawal action, such as removing or taking out funds, resources, or participation from something.
-
C.
withdrawalRequestedBy
Indicates that a withdrawal action has been initiated or requested by a specific entity.
-
D.
withdrawnDuring
Indicates that something is removed, canceled, or taken back over the course of a specified time period or event.
-
E.
withdrawalEnd
Indicates the point in time or condition at which a withdrawal process or right comes to an end.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f934be208190aed5a7f6a44b6b83 |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 4:12 p.m.