Triple
T1459294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presto card |
E31472
|
entity |
| Predicate | supportsTapOnTapOff |
P29000
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Presto card, supportsTapOnTapOff, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTapOnTapOff Context triple: [Presto card, supportsTapOnTapOff, true]
-
A.
supportsTapToPay
Indicates that an entity enables or is compatible with tap-to-pay (contactless) payment functionality.
-
B.
hasVIPTerminal
Indicates that one entity possesses or provides access to a VIP (very important person) terminal associated with another entity.
-
C.
supportsDeviceCount
Indicates the number of devices that a system, service, or component is capable of supporting concurrently.
-
D.
hasSecurityTerminal
Indicates that an entity is equipped with or contains a security terminal used for access control, monitoring, or security-related operations.
-
E.
canBeUsedOver
Indicates that one entity is suitable or valid for use in place of, or in relation to, another entity.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59c1c288190be08064f2d351b2b |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c52bbb748190aaa804438d31f4c2 |
completed | March 1, 2026, 11 p.m. |
Created at: March 1, 2026, 8 p.m.