Triple
T1338416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OV-chipkaart |
E28408
|
entity |
| Predicate | requiresCheckIn |
P27909
|
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, requiresCheckIn, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresCheckIn Context triple: [OV-chipkaart, requiresCheckIn, yes]
-
A.
requiresPresence
Indicates that one entity’s existence, operation, or validity depends on another entity being present or available.
-
B.
creditCheckRequired
Indicates that a verification of an entity’s creditworthiness must be performed before proceeding with a related action or transaction.
-
C.
hasCheckInBuilding
Indicates that an entity has performed a check-in event within a specified building.
-
D.
requiresDataAvailability
Indicates that one entity’s operation, validity, or execution is contingent on the presence, accessibility, or readiness of specific data.
-
E.
requiresShowing
Indicates that one entity must be displayed or made visible as a prerequisite or condition for another entity, action, or state.
- 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_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. |
| PDg | Predicate description generation | batch_69a4c1bf31988190a659f48fe018f4bc |
completed | March 1, 2026, 10:46 p.m. |
Created at: March 1, 2026, 7:56 p.m.