Triple
T4692336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viva Viagem smart card |
E104062
|
entity |
| Predicate | isRechargeable |
P28999
|
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: [Viva Viagem smart card, isRechargeable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRechargeable Context triple: [Viva Viagem smart card, isRechargeable, true]
-
A.
rechargeable
chosen
Indicates that an entity can have its stored energy replenished, typically by being connected to a power source, and thus can be used repeatedly rather than discarded after a single use.
-
B.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
C.
supportsAutoCharge
Indicates that one entity enables or is compatible with automatic charging functionality for another entity.
-
D.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
E.
hasBackupBattery
Indicates that an entity is equipped with an additional battery intended to provide power when the primary power source is unavailable or fails.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.