Triple
T1675746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehran Bus Rapid Transit |
E36226
|
entity |
| Predicate | hasPaymentMethod |
P5428
|
FINISHED |
| Object | prepaid smart card |
—
|
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: prepaid smart card | Statement: [Tehran Bus Rapid Transit, hasPaymentMethod, prepaid smart card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPaymentMethod Context triple: [Tehran Bus Rapid Transit, hasPaymentMethod, prepaid smart card]
-
A.
hasPaymentModel
Indicates that an entity uses, is associated with, or operates under a particular payment model or pricing scheme.
-
B.
paymentMethod
chosen
Indicates the means or instrument through which a payment is made in a transaction.
-
C.
hasStripe
Indicates that one entity possesses or exhibits a stripe or stripes as a characteristic or feature.
-
D.
hasCredit
Indicates that an entity possesses or is assigned a credit, such as financial credit, academic credit, or acknowledgment for a contribution.
-
E.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.