Triple
T3787305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary Reserve |
E85558
|
entity |
| Predicate | payStatus |
P39724
|
FINISHED |
| Object | unpaid when not on duty |
—
|
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: unpaid when not on duty | Statement: [Supplementary Reserve, payStatus, unpaid when not on duty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payStatus Context triple: [Supplementary Reserve, payStatus, unpaid when not on duty]
-
A.
hasPayStatus
chosen
Indicates the current payment state or condition associated with an entity, such as whether an amount is paid, unpaid, pending, or otherwise resolved.
-
B.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
C.
paidFor
Indicates that one entity provided payment to cover the cost of something on behalf of another entity.
-
D.
profitStatus
Indicates the financial performance state of an entity, such as whether it is operating at a profit, loss, or breaking even.
-
E.
isUnpaid
Indicates that an expected payment, fee, or financial obligation has not yet been made or settled.
- 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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d3c92c819081d9d5c45ef37a5d |
completed | March 9, 2026, 3:14 p.m. |
Created at: March 9, 2026, 3:13 p.m.