Triple
T1270735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mont Blanc du Tacul |
E15701
|
entity |
| Predicate | isOnBorder |
P18258
|
FINISHED |
| Object | near border between France and Italy |
—
|
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: near border between France and Italy | Statement: [Mont Blanc du Tacul, isOnBorder, near border between France and Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnBorder Context triple: [Mont Blanc du Tacul, isOnBorder, near border between France and Italy]
-
A.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
B.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
C.
hasBorderLocality
chosen
Indicates that one locality is situated along or adjacent to the border of another locality.
-
D.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
-
E.
guaranteedBorderBetween
Indicates a formally assured and recognized boundary relationship that definitively separates two regions or entities.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c0691d70819088e57c78ff34af1e |
completed | March 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.