Triple
T16381976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro TAP card |
E397827
|
entity |
| Predicate | reloadability |
P17723
|
FINISHED |
| Object | reloadable |
—
|
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: reloadable | Statement: [Metro TAP card, reloadability, reloadable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reloadability Context triple: [Metro TAP card, reloadability, reloadable]
-
A.
reusability
Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
-
B.
reconfigurability
Indicates the capability of something to be rearranged, adapted, or modified into different configurations or functional setups.
-
C.
reloadTime
Indicates the amount of time required for something (typically a weapon, tool, or system) to be reloaded and made ready for use again.
-
D.
isReloadable
chosen
Indicates that an entity can be loaded again or refreshed, typically after being used, changed, or depleted.
-
E.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319dd0e0c8190812bde6a2f7d9644 |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.