Triple
T25096458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumamoto City Tram |
E628601
|
entity |
| Predicate | usesICCardBrand |
P69490
|
FINISHED |
| Object | PASMO-compatible cards |
—
|
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: PASMO-compatible cards | Statement: [Kumamoto City Tram, usesICCardBrand, PASMO-compatible cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesICCardBrand Context triple: [Kumamoto City Tram, usesICCardBrand, PASMO-compatible cards]
-
A.
compatibleICCardBrand
chosen
Indicates that one entity (such as a device or system) supports and can properly operate with IC cards of the specified brand.
-
B.
issuerBrandPortfolioIncludes
Indicates that an issuer’s overall brand portfolio contains or encompasses a particular brand.
-
C.
cardBrandsInvolved
Indicates that specific payment card brands are involved or participate in a given transaction, process, or context.
-
D.
issuerBrandName
Indicates the brand name associated with the entity that issues a product, document, or instrument.
-
E.
cardFunction
Indicates that one entity serves as the functional role, capability, or purpose associated with a card-related entity in a system.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 6:25 a.m.