Triple
T11894071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilhete Único |
E282990
|
entity |
| Predicate | cardVerificationMethod |
P102113
|
FINISHED |
| Object | tap-in validation |
—
|
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: tap-in validation | Statement: [Bilhete Único, cardVerificationMethod, tap-in validation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardVerificationMethod Context triple: [Bilhete Único, cardVerificationMethod, tap-in validation]
-
A.
cardFunction
Indicates that one entity serves as the functional role, capability, or purpose associated with a card-related entity in a system.
-
B.
cardType
Indicates the classification or category assigned to a card within a given system or context.
-
C.
cardTypeAccess
Indicates that access or permissions are determined or constrained based on the type of card involved.
-
D.
cardRequiredFor
Indicates that a specific card must be presented or possessed in order to access, use, or complete the related item, service, or action.
-
E.
cardFormat
Indicates the specific layout or structural style in which a card or card-like item is presented or encoded.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd1172988190a2c13d37220f2f93 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:44 p.m.