Triple
T37147086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col de Panissars |
E920268
|
entity |
| Predicate | onModernBorderBetween |
P60490
|
FINISHED |
| Object | France |
—
|
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: France | Statement: [Col de Panissars, onModernBorderBetween, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onModernBorderBetween Context triple: [Col de Panissars, onModernBorderBetween, France]
-
A.
onBorderBetween
Indicates that an entity is located along or directly adjacent to the dividing line shared by two distinct regions or areas.
-
B.
nearModernBorderWith
chosen
Indicates that one entity is located close to the present-day political or geographic border shared with another entity.
-
C.
isDividedByModernBorder
Indicates that a single entity or area is split into separate parts by a contemporary political or administrative boundary.
-
D.
laterFormedBorderBetween
Indicates that the relationship or boundary between two entities was established at a later time, forming a border between them after an earlier period or state.
-
E.
adjustedBorderBetween
Indicates that the boundary separating two entities has been modified or realigned from its previous position.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.