Triple
T37856709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keihan fare system |
E944211
|
entity |
| Predicate | supportsCard |
P105566
|
FINISHED |
| Object | ICOCA |
E71900
|
NE 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: ICOCA | Statement: [Keihan fare system, supportsCard, ICOCA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCard Context triple: [Keihan fare system, supportsCard, ICOCA]
-
A.
supportsCardRegistration
Indicates that an entity provides the capability to register a payment or identification card for use within a system or service.
-
B.
supportsLoyaltyCards
Indicates that an entity provides functionality to accept, manage, or work with loyalty cards for rewards or benefits.
-
C.
usesCard
Indicates that an entity employs or relies on a specific card (e.g., payment, access, or identification card) to perform an action or participate in an interaction.
-
D.
personalizedCardSupports
Indicates that a personalized card is compatible with, or can be used in conjunction with, a particular system, service, or feature.
-
E.
supportsSmartcards
chosen
Indicates that one entity provides compatibility with or the ability to use smartcard-based functionality for another entity.
- F. None of above.
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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40fb889d04819089c1c1651fc7da9b |
completed | June 28, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.