Triple
T31329238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navigo Découverte |
E798978
|
entity |
| Predicate | topUpUnit |
P27918
|
FINISHED |
| Object | time-based passes |
—
|
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: time-based passes | Statement: [Navigo Découverte, topUpUnit, time-based passes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topUpUnit Context triple: [Navigo Découverte, topUpUnit, time-based passes]
-
A.
topUpMethod
Indicates the method or mechanism used to add funds or value to an account, balance, or service.
-
B.
topUpLocations
chosen
Indicates locations where a balance, credit, or value can be increased or recharged for a related account, service, or device.
-
C.
upgradeTargetUnits
Indicates that certain units are designated to be improved or converted to a higher or more advanced version.
-
D.
rechargeType
Indicates the method or mechanism by which something is replenished, refilled, or re-energized.
-
E.
supportedUnit
Indicates that one entity provides assistance, resources, or backing to another entity functioning as a unit or sub-organization.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69ede2ea48190999b3d041f7bf55e |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:16 p.m.