Triple
T12287457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mont Perdut |
E292865
|
entity |
| Predicate | formsBorderLandscapeWith |
P43209
|
FINISHED |
| Object | Gavarnie area in France |
—
|
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: Gavarnie area in France | Statement: [Mont Perdut, formsBorderLandscapeWith, Gavarnie area in France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsBorderLandscapeWith Context triple: [Mont Perdut, formsBorderLandscapeWith, Gavarnie area in France]
-
A.
partlyFormsBorderBetween
Indicates that one entity constitutes only a portion of the boundary separating two other entities.
-
B.
recognizedBorder
Indicates that one entity formally acknowledges and accepts another entity’s boundary as a legitimate border.
-
C.
relatedBorder
chosen
Indicates that two geographic or political entities share a common boundary or border with each other.
-
D.
borderColor
Indicates the color that forms the boundary or outline of an entity.
-
E.
supportsBorders
Indicates that one entity endorses, maintains, or upholds the existence or enforcement of boundaries or borders associated with another entity.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9261e1570819084bb4fdb44aa6aea |
completed | April 10, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69d91c4d9a9c8190aeb7beaf9792d8f0 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.