Triple
T28772421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navigo Annuel |
E726446
|
entity |
| Predicate | cancellationConditions |
P165788
|
FINISHED |
| Object | subject to notice period |
—
|
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: subject to notice period | Statement: [Navigo Annuel, cancellationConditions, subject to notice period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cancellationConditions Context triple: [Navigo Annuel, cancellationConditions, subject to notice period]
-
A.
cancellationReason
Indicates the reason or cause for which a previously scheduled or planned action, event, or agreement was canceled.
-
B.
cancellation
Indicates that a previously planned or scheduled event, action, or agreement is being annulled, terminated, or rendered no longer valid.
-
C.
canceledAfter
Indicates that one event or action was canceled at a point in time occurring after another specified event or action.
-
D.
canceledBy
Indicates that an action, event, or agreement was annulled or called off by a specific entity.
-
E.
canceledBefore
Indicates that one event, reservation, or commitment was canceled at a time earlier than another specified event or reference point.
- F. None of above. chosen
Provenance (4 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 28, 2026, 6:16 a.m.