Triple
T17174837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | METRO Q Card |
E416831
|
entity |
| Predicate | reloadable |
P17723
|
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: [METRO Q Card, reloadable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reloadable Context triple: [METRO Q Card, reloadable, true]
-
A.
isReloadable
chosen
Indicates that an entity can be loaded again or refreshed, typically after being used, changed, or depleted.
-
B.
isReloadableOnline
Indicates that an item, service, or account balance can be replenished or topped up through an online process.
-
C.
removable
Indicates that one entity can be detached, taken off, or separated from another without causing damage or permanent alteration.
-
D.
reconfigurability
Indicates the capability of something to be rearranged, adapted, or modified into different configurations or functional setups.
-
E.
rechargeable
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.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0c329081909f118bd4b7be8653 |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.