Triple
T36217558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portalet |
E1047739
|
entity |
| Predicate | hasBorderCrossingBetween |
P4105
|
FINISHED |
| Object | Spain |
—
|
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: Spain | Statement: [Portalet, hasBorderCrossingBetween, Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderCrossingBetween Context triple: [Portalet, hasBorderCrossingBetween, Spain]
-
A.
hasBorderCrossing
chosen
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
-
B.
hasBorderCrossingsType
Indicates that a border crossing is classified by a specific type or category of crossing (e.g., road, rail, pedestrian, maritime).
-
C.
hasBorderCrossingSide
Indicates that one side of a border crossing is associated with or located on a particular boundary or segment of that crossing.
-
D.
hasRailBorderCrossing
Indicates that two places are connected by at least one official border crossing that is served by rail transport.
-
E.
hasBorderCrossingStatus
Indicates whether a border crossing is open, closed, restricted, or otherwise classified in terms of its operational or legal status.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 3, 2026, 4:09 p.m.