Triple
T2477862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selected Reserve |
E55130
|
entity |
| Predicate | hasPayStatus |
P39724
|
FINISHED |
| Object | members receive drill pay |
—
|
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: members receive drill pay | Statement: [Selected Reserve, hasPayStatus, members receive drill pay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPayStatus Context triple: [Selected Reserve, hasPayStatus, members receive drill pay]
-
A.
hasPaidTransfer
Indicates that a transfer of something (such as money, ownership, or rights) has been completed through a payment.
-
B.
hasPaymentModel
Indicates that an entity uses, is associated with, or operates under a particular payment model or pricing scheme.
-
C.
isUnpaid
Indicates that an expected payment, fee, or financial obligation has not yet been made or settled.
-
D.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
E.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
- 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_69ab49e279e88190ab10d7248aea9d11 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1e45380819094b3f32a278bd457 |
completed | March 7, 2026, 7:21 a.m. |
Created at: March 6, 2026, 9:45 p.m.