Triple
T31329233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navigo Découverte |
E798978
|
entity |
| Predicate | canBeBlocked |
P93397
|
FINISHED |
| Object | no personal blocking by name on standard card |
—
|
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: no personal blocking by name on standard card | Statement: [Navigo Découverte, canBeBlocked, no personal blocking by name on standard card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeBlocked Context triple: [Navigo Découverte, canBeBlocked, no personal blocking by name on standard card]
-
A.
canBlock
Indicates that one entity has the ability or permission to prevent, obstruct, or stop the action or effect of another entity.
-
B.
canBeBlockedWhenLost
Indicates that an item, once lost, is capable of being deactivated or blocked to prevent further use or access.
-
C.
canBeLocked
chosen
Indicates that an entity has the capability to be secured or made inaccessible by applying a lock or locking mechanism.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
isBarred
Indicates that an entity is officially prohibited or excluded from participating in, entering, or accessing another entity or activity.
- 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_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: April 29, 2026, 9:16 p.m.