Triple
T10341891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visa Information System |
E243144
|
entity |
| Predicate | dataRetentionPeriod |
P93788
|
FINISHED |
| Object | 5 years for most visa application data |
—
|
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: 5 years for most visa application data | Statement: [Visa Information System, dataRetentionPeriod, 5 years for most visa application data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataRetentionPeriod Context triple: [Visa Information System, dataRetentionPeriod, 5 years for most visa application data]
-
A.
documentationPeriod
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
-
B.
retentionMethod
Indicates the method or strategy used to retain or keep something (such as data, customers, or resources) over time.
-
C.
removalPeriod
Indicates the time span during which something is taken away, deleted, or otherwise removed from availability or consideration.
-
D.
existencePeriod
Indicates the time span during which an entity exists or is valid.
-
E.
detentionPolicy
Indicates the rules or conditions under which individuals may be held in custody or confinement.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 11:55 a.m.