Triple
T10561355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troika card |
E249223
|
entity |
| Predicate | canBeRecharged |
P28999
|
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: [Troika card, canBeRecharged, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeRecharged Context triple: [Troika card, canBeRecharged, yes]
-
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.
canHoldAdditionalChargeOf
Indicates that one entity has the capacity to store or accommodate an additional specified amount of electric charge beyond its current level.
-
C.
supportsAutoCharge
Indicates that one entity enables or is compatible with automatic charging functionality for another entity.
-
D.
rechargeSource
Indicates that one entity serves as the power or energy provider used to recharge another entity.
-
E.
requiresCharging
Indicates that an entity depends on being recharged (e.g., with electrical power or energy) in order to function or continue operating.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52720621c8190a1126268ebe57c83 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.