Triple
T13612809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PC Optimum |
E325234
|
entity |
| Predicate | supportsCardlessIdentification |
P110419
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [PC Optimum, supportsCardlessIdentification, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCardlessIdentification Context triple: [PC Optimum, supportsCardlessIdentification, yes]
-
A.
supportsIdentity
Indicates that one entity upholds, validates, or reinforces the identity, self-concept, or role of another entity.
-
B.
supportsTapToPay
Indicates that an entity enables or is compatible with tap-to-pay (contactless) payment functionality.
-
C.
supportsAccountType
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
-
D.
hasPhysicalCard
Indicates that an entity possesses or is associated with a tangible, real-world card object.
-
E.
canUphold
Indicates that an entity has the ability or capacity to maintain, support, or sustain another entity, condition, or standard.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbbb8c77dc8190b7bd803b5e168d23 |
completed | April 12, 2026, 3:34 p.m. |
Created at: April 9, 2026, 9:50 p.m.