Triple
T885022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croatia |
E19110
|
entity |
| Predicate | SchengenEntryDate |
P21386
|
FINISHED |
| Object | 2023-01-01 |
—
|
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: 2023-01-01 | Statement: [Croatia, SchengenEntryDate, 2023-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SchengenEntryDate Context triple: [Croatia, SchengenEntryDate, 2023-01-01]
-
A.
hasSchengenArea
Indicates that a place, country, or region is part of, or included within, the Schengen Area for border-free movement.
-
B.
hasBorderControlStatus
Indicates the type or condition of border control that applies to a given entity or location.
-
C.
arrivalInEurope
Indicates the event or state of something or someone reaching or entering a location within Europe.
-
D.
enteredMontevideoDate
Indicates the date on which an entity arrived in or entered Montevideo.
-
E.
hasBorderCrossing
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
- 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_69a4939c32488190a7ccd41cf0abb22b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ae787bf081909533082ca013624a |
completed | March 1, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8ff8c48190a33b00acf65c1276 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ae774fac8190b3134d64086d65fe |
completed | March 1, 2026, 9:24 p.m. |
Created at: March 1, 2026, 7:39 p.m.