Triple
T16140124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Valinco |
E391630
|
entity |
| Predicate | hasNearbyMountainousInterior |
P45689
|
FINISHED |
| Object | Corsican interior mountains |
—
|
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: Corsican interior mountains | Statement: [Gulf of Valinco, hasNearbyMountainousInterior, Corsican interior mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyMountainousInterior Context triple: [Gulf of Valinco, hasNearbyMountainousInterior, Corsican interior mountains]
-
A.
hasMountainousTerrain
chosen
Indicates that a location or area possesses predominantly mountainous physical terrain or landscape features.
-
B.
hasNearestMountain
Indicates that one entity is the closest mountain geographically relative to another entity.
-
C.
hasMountain
Indicates that a location or region possesses or contains at least one mountain.
-
D.
hasMountainPassNearby
Indicates that a mountain pass is located in close proximity to the referenced place or feature.
-
E.
hasAncestralMountain
Indicates that an entity has a specific mountain recognized as its ancestral place of origin or heritage.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a07b7908190b4e1ec57f60a9274 |
completed | April 17, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.