Triple
T19939996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astromeritis–Zodeia crossing |
E479282
|
entity |
| Predicate | hasCheckpointInfrastructure |
P137917
|
FINISHED |
| Object | customs control |
—
|
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: customs control | Statement: [Astromeritis–Zodeia crossing, hasCheckpointInfrastructure, customs control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckpointInfrastructure Context triple: [Astromeritis–Zodeia crossing, hasCheckpointInfrastructure, customs control]
-
A.
hasCheckpoint
Indicates that an entity includes, contains, or is associated with one or more intermediate control or verification points within its structure, process, or path.
-
B.
hasCheckpointControl
Indicates that one entity exercises control, management, or authority over a checkpoint associated with another entity.
-
C.
hasCheckpointType
Indicates that a checkpoint is associated with a specific type or category defining its role or characteristics.
-
D.
hadCheckpoint
Indicates that an entity passed through, reached, or was associated with a specific checkpoint at some point in time.
-
E.
supportsCheckpointRestore
Indicates that an entity provides the capability to save its execution state as a checkpoint and later restore operation from that saved 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a19d77c819088bce99c94568d0d |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.