Triple
T30242949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyšné Nemecké |
E768970
|
entity |
| Predicate | usedAsEntryPointTo |
P2506
|
FINISHED |
| Object | Schengen Area |
—
|
NE NERFINISHED |
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: Schengen Area | Statement: [Vyšné Nemecké, usedAsEntryPointTo, Schengen Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsEntryPointTo Context triple: [Vyšné Nemecké, usedAsEntryPointTo, Schengen Area]
-
A.
usedAsProgramFor
Indicates that one entity functions as the software or application used to operate, control, or provide services for another entity.
-
B.
isUsedAs
chosen
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
C.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
D.
usedAsSourceIn
Indicates that something serves as the origin, basis, or input from which another thing is derived, produced, or obtained.
-
E.
usedForLaunchOf
Indicates that something serves as the means, tool, or platform by which a launch (such as of a product, mission, or event) is carried out.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:39 p.m.