Triple
T28435623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TIMS card |
E715253
|
entity |
| Predicate | feePaidIn |
P164725
|
FINISHED |
| Object | Nepalese rupees |
—
|
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: Nepalese rupees | Statement: [TIMS card, feePaidIn, Nepalese rupees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feePaidIn Context triple: [TIMS card, feePaidIn, Nepalese rupees]
-
A.
paidFor
Indicates that one entity provided payment to cover the cost of something on behalf of another entity.
-
B.
feeStatus
Indicates the current state or condition of fees associated with an entity, such as whether they are due, paid, waived, or overdue.
-
C.
paidBy
Indicates that a payment or financial obligation is made or settled by the specified entity.
-
D.
chargesWere
Indicates that specific accusations or legal charges existed or were formally brought against an entity at some point in time.
-
E.
chargesFeeFor
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64ee0c2788190a94a04ad1902fd5e |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64e36c57c8190af09470a8d35512b |
completed | May 2, 2026, 7:19 p.m. |
Created at: April 28, 2026, 1:42 a.m.