Triple
T1338422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OV-chipkaart |
E28408
|
entity |
| Predicate | canBeAutoReloaded |
P15669
|
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: [OV-chipkaart, canBeAutoReloaded, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAutoReloaded Context triple: [OV-chipkaart, canBeAutoReloaded, yes]
-
A.
allowsAutoReload
chosen
Indicates that one entity permits another entity or process to automatically reload or refresh without manual intervention.
-
B.
isReloadable
Indicates that an entity can be loaded again or refreshed, typically after being used, changed, or depleted.
-
C.
canBeLoadedAt
Indicates that an entity is capable of being placed onto or into another entity (such as a vehicle, container, or system) at a specific location or point in time.
-
D.
canBeAdaptedBy
Indicates that one entity is capable of being modified, adjusted, or tailored for use by another entity.
-
E.
isRenewable
Indicates that a resource or energy source can be naturally replenished or regenerated within a human-relevant timescale.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c2115d388190b031ae2de1296f8a |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.